GDM won't start, hangs in upstart on "emit starting-dm"
Bug #439316 reported by
rojer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| usplash (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Bug Description
Binary package hint: gdm
Latest change indictaes that emitting an upstart signal was added.
This broke GDM on my machine - emitting signal gets stuck and gdm does not start.
Logging in on the console and killing the initctl process resumes GDM startup.
See attached screenshot 1 for boot process - it gets stuck at this point. Note that my default DM is GDM even though boot screen complains about KDM.
Screenshot 2 is taken on tty1 and shows what needs to be done to get GDM running.
Revision history for this message
| rojer (rojer9) wrote | #1 |
Revision history for this message
| rojer (rojer9) wrote | #2 |
Revision history for this message
| Colin Watson (cjwatson) wrote | #3 |
| affects: | gdm (Ubuntu) → usplash (Ubuntu) |
| Changed in usplash (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Colin Watson (cjwatson) wrote | #4 |
| Changed in usplash (Ubuntu): | |
| importance: | Undecided → High |
Revision history for this message
| rojer (rojer9) wrote | #5 |
| Changed in usplash (Ubuntu): | |
| status: | Incomplete → New |
Revision history for this message
| Fausto Piovesan (faustop) wrote | #6 |
Revision history for this message
| Phillip Susi (psusi) wrote | #7 |
| Changed in usplash (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
initctl emit is supposed to block until the upstart jobs hung off that event complete, so this is more likely to be usplash's fault. Could you grep for usplash processes instead of gdm, and show us what's running there?
I suspect that 'usplash_write QUIT' is blocking because nothing is listening on the usplash FIFO, in which case the only reliable fix for this is likely to be sorting out the usplash main loop so that we can just send it SIGTERM.