[Bug 873027] Re: DBUS_STARTER_ADDRESS and DBUS_STARTER_BUS_TYPE aren't always unset from environment making gedit and possibly others fail to start

[James M. Leddy]

Thanks for the heads up. I accidentally cherry picked from the devel
branch, which caused the issue. The resubmission should be good.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/873027

Title:
  DBUS_STARTER_ADDRESS and DBUS_STARTER_BUS_TYPE aren't always unset
  from environment making gedit and possibly others fail to start

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project oneiric series:
  In Progress
Status in Unity 2D:
  Fix Released
Status in “unity-2d” package in Ubuntu:
  Fix Released
Status in “unity-2d” source package in Oneiric:
  In Progress
Status in “unity-2d” source package in Precise:
  Fix Released

Bug description:
  SRU note:

  [Impact]

  Anyone using unity-2d and also using gedit, which can affect a number
  of machines for which there are no 3d drivers, eg underpowered
  netbooks.

  [Test Case]

  1) Switch to unity-2d on login
  2) Start up Gedit
  3) observe gedit does not start

  [Regression Potential]
  Small, we've been running this patch in precise without issue. Additionally, it's just a 3 line change to unset an env variable.

  Original report:

  ISO testing showed that sometimes, only on Unity 2D (so far),
  DBUS_STARTER_ADDRESS and DBUS_STARTER_BUS_TYPE aren't unset from the
  environment when starting a new software.

  This breaks gedit as it's actually checking these variables for its
  own DBUS activation

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/873027/+subscriptions