[enhancement] Disable XMir if fails to start
Bug #1195539 reported by
Robert Ancell
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Light Display Manager |
Triaged
|
Medium
|
Unassigned | ||
| Unity System Compositor |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Currently we try to fall back to traditional X if XMir fails to start. In some cases we're seeing that not work which can leave a system in an unbootable state. Err on the side of caution and if XMir fails to start then next boot just don't try it at all. The user will have to do a manual intervention (e.g. remove a lock file from /var) to re-enable it.
| Changed in lightdm: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Robert Ancell (robert-ancell) wrote | #1 |
| tags: | added: xmir |
| summary: |
- Disable XMir if fails to start + [enhancement] Disable XMir if fails to start |
| tags: | added: enhancement |
To post a comment you must log in.
Was thinking about this over the weekend.. The risk of latching XMir off is any minor problem might cause XMir to be disabled forever unless the user is particularly vigilant. A safer method might be to disable XMir the next time if it has failed and clear that flag when it runs successfully. In this case the user will get one attempt to fix it before the next boot.