It is now a year since this bug was marked "Critical", but it keeps being postponed. I think this was part of the cause of an embarrassing experience during my recent presentation to a Linux Users Group, where Unity went away twice, forcing me to reboot the first time, and borrow a (gasp!) Apple computer the second time to finish the presentation.
What is the status of the overall fix? What is the story with the "fix released" aspect of this for gnome-session? Was that just one aspect of the fix? When it is fixed, will it be backported to Trusty? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1308800 Title: Unity doesn't respawn all the times on crashes Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in gnome-session package in Ubuntu: Fix Released Status in unity package in Ubuntu: In Progress Bug description: [Impact] Killing compiz repeatedly doesn't make unity to reload all the times. This is caused by the fact that due to a regression unity7 is not loaded anymore by upstart (but by gnome-session) and thus it seems that sometimes it doesn't properly gets restarted. This is also a security issue, because if the session was locked, and unity is not reloaded the session won't be locked anymore. [Test Case] From a terminal run killall -9 compiz multiple times, it should always reload, but it fails after a couple of times. [Regression Potential] The fix is about always making unity to be launched by upstart. Regression potential is low, since upstart is now used by most ubuntu desktop applications, and it ensures compiz will run properly anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
