[Bug 1234731] [NEW] DBus jobs not setting environment variables

[Ted Gould]

Public bug reported:


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...

** Affects: hud
     Importance: Undecided
         Status: Incomplete

** Affects: url-dispatcher
     Importance: Undecided
         Status: Incomplete

** Affects: dbus (Ubuntu)
     Importance: Undecided
         Status: Confirmed

** Also affects: hud
   Importance: Undecided
       Status: New

** Changed in: hud
       Status: New => Incomplete

** Also affects: url-dispatcher
   Importance: Undecided
       Status: New

** Changed in: url-dispatcher
       Status: New => Incomplete

** Changed in: dbus (Ubuntu)
       Status: New => Confirmed

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

Title:
  DBus jobs not setting environment variables

Status in Unity HUD:
  Incomplete
Status in URL Dispatcher:
  Incomplete
Status in “dbus” package in Ubuntu:
  Confirmed

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