X starts on wrong tty because gdm starts before nvidia driver is ready
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm (Ubuntu) |
Incomplete
|
High
|
Unassigned | ||
Lucid |
Confirmed
|
Undecided
|
Unassigned | ||
Maverick |
Incomplete
|
High
|
Unassigned | ||
nvidia-graphics-drivers (Ubuntu) |
Incomplete
|
High
|
Unassigned | ||
Lucid |
Confirmed
|
Undecided
|
Unassigned | ||
Maverick |
Incomplete
|
High
|
Unassigned |
Bug Description
This bug has been repurposed based on the comments beginning at #15. The original submitter's bug was a duplicate of bug #626723.
When booting certain systems with fast disks, gdm will start up and attempt to launch X before the nvidia kernel driver has fully initialized. This results in gdm restarting X again, without the 'vt7' argument, which may cause X's first-available-VT autoselection to pick a VT between 1 and 6 because the getty jobs have not all yet started. Ultimately this leads to X crashing when pressing certain keys (such as Enter or '2') because the tty has been set into a mode by getty that X is not prepared to handle.
This bug is currently only reported against lucid.
affects: | xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu) |
Changed in xserver-xorg-video-ati (Ubuntu): | |
status: | New → Confirmed |
tags: | added: crash |
Changed in plymouth (Ubuntu): | |
status: | New → Confirmed |
Changed in plymouth (Ubuntu): | |
importance: | Undecided → Medium |
Changed in plymouth (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in plymouth (Ubuntu): | |
status: | Triaged → Confirmed |
Changed in plymouth (Ubuntu): | |
importance: | Medium → High |
tags: | added: patch |
description: | updated |
summary: |
- X starts on wrong tty: pressing enter after 5 minutes crashes X + X starts on wrong tty: pressing enter after 5 minutes crashes X; gdm + restart of X involved |
summary: |
- X starts on wrong tty: pressing enter after 5 minutes crashes X; gdm - restart of X involved + X starts on wrong tty because gdm starts before nvidia driver is ready |
description: | updated |
affects: | plymouth (Ubuntu Maverick) → gdm (Ubuntu Maverick) |
affects: | xserver-xorg-video-ati (Ubuntu Maverick) → nvidia-graphics-drivers (Ubuntu Maverick) |
Changed in nvidia-graphics-drivers (Ubuntu Maverick): | |
status: | Invalid → Confirmed |
description: | updated |
tags: |
added: lucid removed: maverick |
Changed in nvidia-graphics-drivers (Ubuntu Lucid): | |
status: | New → Confirmed |
Changed in gdm (Ubuntu Maverick): | |
status: | Confirmed → New |
Changed in nvidia-graphics-drivers (Ubuntu Maverick): | |
status: | Confirmed → Incomplete |
Changed in gdm (Ubuntu Maverick): | |
status: | New → Incomplete |
Changed in gdm (Ubuntu Lucid): | |
status: | New → Confirmed |
Changed in nvidia-graphics-drivers (Ubuntu Maverick): | |
importance: | Medium → High |
This part of the Gdm 1 log is suspicious:
Backtrace: +0x3b) [0x80e83bb] rt_sigreturn+ 0x0) [0xc0840c] start_main+ 0xe7) [0x3c8ce7]
0: /usr/bin/X (xorg_backtrace
1: /usr/bin/X (0x8048000+0x5da8d) [0x80a5a8d]
2: (vdso) (__kernel_
3: /usr/bin/X (0x8048000+0x25d3e) [0x806dd3e]
4: /usr/bin/X (0x8048000+0x1a5ba) [0x80625ba]
5: /lib/libc.so.6 (__libc_
6: /usr/bin/X (0x8048000+0x1a191) [0x8062191]
Caught signal 3 (Quit). Server aborting
Please consult the The X.Org Foundation support wiki.x. org Xorg.0. log" for additional information.
at http://
for help.
Please also check the log file at "/var/log/