if xorg exits too early, lightdm should retry starting xorg without -mir
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Case of today:
- initializing xorg with -mir fails on ati, it exits on: [drm] failed to set drm interface version. (see dmesg http://
lightdm then:
[+1.41s] DEBUG: Starting X server on Unity compositor
[+1.41s] DEBUG: Using VT 7
[+1.41s] DEBUG: Logging to /var/log/
[+1.41s] DEBUG: Writing X server authority to /var/run/
[+1.41s] DEBUG: Launching X Server
[+1.41s] DEBUG: Launching process 4202: /usr/bin/X -core :0 -auth /var/run/
[+1.41s] DEBUG: Waiting for ready signal from X server :0
[+1.56s] DEBUG: Process 4202 terminated with signal 6
[+1.56s] DEBUG: X server stopped
[+1.56s] DEBUG: Removing X server authority /var/run/
[+1.56s] DEBUG: Releasing VT 7
[+1.56s] DEBUG: Display server stopped
-> it tried it twice, as you can see on http://
Shouldn't lightdm tries to start xorg with -mir (it's weird I don't see that on logs, so maybe there is something else…), then fallback to traditional xorg if xorg -mir exited too early?
version installed: https:/
tags: | added: entering-saucy |
summary: |
- if unity-system-compositor exits too early, lightdm should retry - starting xorg without -mir + if xorg exits too early, lightdm should retry starting xorg without -mir |
description: | updated |
Changed in mir: | |
milestone: | none → 0.0.9 |
status: | Fix Committed → Fix Released |
This is solved by making unity-system- compositor depend on XMir. So you can't have the system compositor running without XMir available.