crash during oneiric->precise upgrade leaving screen black while the upgrade was running
Bug #956108 reported by
Michael Vogt
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Compiz Core |
Won't Fix
|
Undecided
|
Unassigned | ||
| compiz (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
| Precise |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
Compiz crashed during a oneiric->precise upgrade leaving the screen blank without any chance to interact with the
machine anymore.
Revision history for this message
| Michael Vogt (mvo) wrote | #1 |
| summary: |
- crash during oneiric->precise upgrade + crash during oneiric->precise upgrade leaving screen black while the + upgrade was running |
| Changed in compiz (Ubuntu): | |
| importance: | Undecided → High |
| tags: | added: precise rls-mgr-p-tracking |
Revision history for this message
| David Barth (dbarth) wrote | #2 |
| Changed in compiz (Ubuntu Precise): | |
| status: | New → Won't Fix |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in compiz (Ubuntu): | |
| status: | New → Confirmed |
| Changed in compiz (Ubuntu): | |
| status: | Confirmed → Won't Fix |
| Changed in compiz-core: | |
| status: | New → Won't Fix |
To post a comment you must log in.
The root cause is that update-manager can change the executable or libs that compiz depend on and a page fault can bring an inconsistent segment into memory.
We don't have a good way to protect against that. We're not guaranteed that restarting compiz would work, since that may trigger this page fault. Besides compiz rdeps that rely on its ABI need to be upgraded in the order for it to succeed. Unity is such an example.
As a workaround post-precise, we may try to use something like mlockall to mount all pages in memory upon the reception of a signal to protect compiz from such a scenario. And then restart. This is an hypothesis and we can't really commit to it for this cycle.