[Bug 1234731] Re: calling 'initctl set-env -g' from within an upstart job is lost

[Steve Langasek]

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 why yet.  I've done 10+ guest login sessions,
5+ logins with a second account on my system, and a restart of my
regular user's session, and have yet to reproduce the bug again after
adding debugging info to the upstart package here.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1234731

Title:
  calling 'initctl set-env -g' from within an upstart job is lost

Status in Unity HUD:
  Invalid
Status in URL Dispatcher:
  Invalid
Status in “dbus” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  New

Bug description:
  
  This is an attempt to try to bring a bunch of information together that seems all over the place right now.  I'll try to add what we think I know, but let's everyone try to put other information here as we get it.

  It seems that on some situations Upstart jobs are started that don't
  have the DBUS_SESSION_BUS_ADDRESS environment variable set, even
  though they're "start on started dbus" in their Upstart job.  The
  cases I've seen are for HUD and URL Dispatcher though I'm suspicious
  that indicator-datetime is seeing it as well.  The interesting part
  about these jobs is that one is DBus Activation based (HUD) so we know
  that the DBus job has run and DBus is alive and well.

  Kindly, the URL Launch one happened under testing so we have lots of
  logs:

  http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4525/music-app-
  autopilot/

  The error that URL dispatcher is reporting is that its connection was
  refused:

  https://jenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-music-
  app-autopilot/101/artifact/clientlogs/url-dispatcher.log/*view*/

  And when we look at its environment it is shockingly blank:

  https://jenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-music-
  app-autopilot/101/artifact/clientlogs/_usr_lib_arm-linux-
  gnueabihf_url-dispatcher_url-dispatcher.32011.crash/*view*/

  The dbus job implies that this can't really happen, but it does...

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/1234731/+subscriptions