Unity doesn't respawn all the times on crashes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Unity |
In Progress
|
Critical
|
Marco Trevisan (Treviño) | |
| | 7.2 |
In Progress
|
Critical
|
Marco Trevisan (Treviño) | |
| | gnome-session (Ubuntu) |
Critical
|
Marco Trevisan (Treviño) | ||
| | Xenial |
Critical
|
Marco Trevisan (Treviño) | ||
| | unity (Ubuntu) |
Critical
|
Marco Trevisan (Treviño) | ||
| | Xenial |
Critical
|
Marco Trevisan (Treviño) | ||
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.
Related branches
- PS Jenkins bot: Approve (continuous-integration) on 2014-04-17
- Brandon Schaefer (community): Approve on 2014-04-17
-
Diff: 23 lines (+0/-11)1 file modifieddebian/unity7.conf (+0/-11)
- Martin Pitt: Approve on 2014-06-04
-
Diff: 79 lines (+25/-10)3 files modifieddata/ubuntu.session.desktop.in.in (+1/-1)
debian/changelog (+7/-0)
debian/patches/50_ubuntu_sessions.patch (+17/-9)
| Changed in unity (Ubuntu): | |
| status: | New → Confirmed |
| assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
| Changed in unity: | |
| milestone: | 7.1.2 → 7.2.1 |
| description: | updated |
| Changed in unity: | |
| status: | Triaged → In Progress |
| Changed in unity (Ubuntu): | |
| status: | Confirmed → In Progress |
| Changed in gnome-session (Ubuntu): | |
| status: | New → In Progress |
| assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
| Changed in unity (Ubuntu): | |
| importance: | Undecided → Critical |
| Marco Trevisan (Treviño) (3v1n0) wrote : | #1 |
| Changed in unity: | |
| assignee: | Marco Trevisan (Treviño) (3v1n0) → Irfan Fauzan (irfan-it2988) |
| Changed in unity (Ubuntu): | |
| assignee: | Marco Trevisan (Treviño) (3v1n0) → Irfan Fauzan (irfan-it2988) |
| Changed in gnome-session (Ubuntu): | |
| status: | In Progress → Fix Committed |
| Launchpad Janitor (janitor) wrote : | #2 |
This bug was fixed in the package gnome-session - 3.9.90-0ubuntu13
---------------
gnome-session (3.9.90-0ubuntu13) utopic; urgency=medium
* 50_ubuntu_
RequiredCom
-- Marco Trevisan (Trevino) <mail@3v1n0.net> Wed, 04 Jun 2014 14:26:54 +0200
| Changed in gnome-session (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Changed in unity: | |
| milestone: | 7.2.1 → 7.2.2 |
| Changed in unity: | |
| assignee: | Irfan Fauzan (irfan-it2988) → Marco Trevisan (Treviño) (3v1n0) |
| Changed in unity (Ubuntu): | |
| assignee: | Irfan Fauzan (irfan-it2988) → Marco Trevisan (Treviño) (3v1n0) |
| Changed in unity: | |
| milestone: | 7.2.2 → 7.2.3 |
| Changed in unity: | |
| milestone: | 7.2.3 → 7.3.1 |
| Changed in unity: | |
| milestone: | 7.3.1 → 7.3.2 |
| Changed in unity: | |
| milestone: | 7.3.2 → 7.3.3 |
| Neal McBurnett (nealmcb) wrote : | #3 |
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!
| Marco Trevisan (Treviño) (3v1n0) wrote : | #4 |
Mhm... Well, the fix was supposed to land in trusty as soon as the fixes for the gnome-keyring bug #1271591 (and related regressions) were backported.
Now this has happened, and we might go ahead, however, I've just noticed that the gnome-session fix needed for this, was overwritten by a merge (http://
Also, the bug #1433013 is somewhat connected to this.
| tags: | added: rls-w-incoming |
| Changed in unity: | |
| milestone: | 7.3.3 → 7.4.0 |
| tags: |
added: rls-x-incoming removed: rls-w-incoming |
| Changed in gnome-session (Ubuntu): | |
| importance: | Undecided → Critical |
| tags: | removed: rls-x-incoming |
| Changed in unity (Ubuntu Xenial): | |
| milestone: | none → ubuntu-16.04 |
| tags: | added: unity-backlog |
| tags: | added: u7-trello-import |
| tags: | removed: u7-trello-import |
| tags: | added: u7-trello-import |
| tags: | removed: u7-trello-import |
| Changed in unity (Ubuntu): | |
| status: | In Progress → Fix Released |
| Changed in unity (Ubuntu Xenial): | |
| status: | In Progress → Fix Released |


Not to get regressions with gnome-keyring, bug #1271591 should be also fixed with this.