lightdm with type=mir causes Ubuntu to freeze on boot. Plymouth progress bar stuck at end.
Bug #1109957 reported by
Daniel van Vugt
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Critical
|
Robert Ancell |
Bug Description
ppa:~rocket-
Plymouth is stuck at 100% progress (all orange dots). However lightdm seemingly is not started. It fails to generate any fresh log files.
This is probably nothing to do with the Mir project. However I can't log it in the public projects of lightdm or plymouth right now. Could just be because the PPA lacks plymouth packages for raring... ?
description: | updated |
summary: |
- /etc/lightdm/lightdm.conf: type=mir causes raring to freeze on reboot. - plymouth stuck at 100% progress. + lightdm with type=mir causes raring to freeze on boot. plymouth stuck at + 100% progress. |
information type: | Proprietary → Public |
summary: |
- lightdm with type=mir causes raring to freeze on boot. plymouth stuck at + lightdm with type=mir causes Ubuntu to freeze on boot. Plymouth stuck at 100% progress. |
Changed in mir: | |
status: | New → Triaged |
Changed in mir: | |
assignee: | nobody → Robert Ancell (robert-ancell) |
Changed in mir: | |
assignee: | Robert Ancell (robert-ancell) → Chris Halse Rogers (raof) |
Changed in mir: | |
assignee: | Chris Halse Rogers (raof) → Robert Ancell (robert-ancell) |
Changed in mir: | |
milestone: | none → 0.0.5 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
Changed in mir: | |
milestone: | 0.0.5 → 0.0.6 |
To post a comment you must log in.
Is there anything useful in /var/log/upstart? It may be that the lightdm starting conditions are not being met for some reason:
start on ((filesystem DEVICE_ FOR_DISPLAY= 1 graphics) )
and runlevel [!06]
and started dbus
and (drm-device-added card0 PRIMARY_
or stopped udev-fallback-
or runlevel PREVLEVEL=S)