[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. ** Description changed: + 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/873027/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
