See bug 1238078.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234731
Title:
calling 'initctl set-env -g' from within an upstart job is lost
To manage notifications about this bug go to:
https://b
** Changed in: dbus (Ubuntu)
Assignee: Dmitrijs Ledkovs (xnox) => (unassigned)
** Changed in: dbus (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/123473
Although looking at my existing login session on my laptop let me
reproduce this problem right off the bat, I've had difficulty
reproducing it again with subsequent login sessions. The problem, once
reproduced, is persistent within upstart, but it's not 100% reproducible
between sessions. No idea
The actual problem here is not caused by dbus startup issues.
/usr/share/upstart/sessions/dbus.conf calls 'initctl set-env -g
DBUS_SESSION_BUS_ADDRESS' on startup, but even after login if I call
'initctl list-env -g', this variable is missing. If I call 'initctl
list-env', it's present - possibly
** Summary changed:
- DBus jobs not setting environment variables
+ calling 'initctl set-env -g' from within an upstart job is lost
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
