Bug #8779
Make start_notification_helper more robust
Start date:
2015-01-22
Due date:
% Done:
0%
Description
On feature/jessie, I see:
Jan 22 18:46:04 amnesia nm-dispatcher[2550]: /etc/NetworkManager/dispatcher.d/20-time.sh: 217: /etc/NetworkManager/dispatcher.d/20-time.sh: cannot open /proc//environ: No such file
Jan 22 18:46:04 amnesia nm-dispatcher[2550]: Script '/etc/NetworkManager/dispatcher.d/20-time.sh' exited with error status 2.
Jan 22 18:46:04 amnesia nm-dispatcher[2550]: /etc/NetworkManager/dispatcher.d/20-time.sh: 217: export: : bad variable name
… which means that in:
GNOME_SHELL_PID="$(pgrep --newest --euid ${LIVE_USERNAME} gnome-shell)"
export "$(tr '\0' '\n' < /proc/${GNOME_SHELL_PID}/environ | \
grep '^DBUS_SESSION_BUS_ADDRESS=')"
… $GNOME_SHELL_PID
is empty. Likely NetworkManager is bootstrapping too fast and GNOME Shell isn’t running yet.
Note that there’s similar code in tails-notify-user
.
Subtasks
Related issues
Is duplicate of Tails - |
Resolved | 2015-01-13 |
History
#1 Updated by intrigeri 2015-01-22 19:28:43
- related to
Bug #8685: Adapt waiting for user notification facilities for Jessie added
#2 Updated by intrigeri 2015-01-22 19:28:56
Next step: confirm that this happens when NM is running in the user session.
#3 Updated by intrigeri 2015-11-10 10:27:34
- related to deleted (
)Bug #8685: Adapt waiting for user notification facilities for Jessie
#4 Updated by intrigeri 2015-11-10 10:27:44
- is duplicate of
Bug #8685: Adapt waiting for user notification facilities for Jessie added
#5 Updated by intrigeri 2015-11-10 10:28:47
- Status changed from Confirmed to Duplicate
I’ve not seen such problems since a while. Perhaps commit:5771f243a5442760d2a12feef28e8caf67801b4e fixes it reliably enough. In any case, this is just the same as Bug #8685, so let’s track it there.