ubuntu-x-swat team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

has anyone reproduced this nvidia+gdm crash on maverick?  Marking
incomplete for maverick pending confirmation.

** Description changed:

+ This bug has been repurposed based on the comments beginning at #15.
+ The original submitter's bug was a duplicate of bug #626723.
  
- After the system boots and the plymouth screen disappears and X starts up on tty1 or tty2, if I press the enter key in a few minutes X shuts down and starts again. In the session of X that comes up after this, the problem doesn't occur.
- 
- The problem happens when gdm starts X and X crashes silently. gdm
- restarts X but X starts on tty1(2) as getty hasn't yet started and it
- isn't the first X start. When getty does start on tty1 it eventually
- interferes with X by setting ISIG on the tty.
- 
- In the cases discussed here, the computer systems are very fast and gdm
- is starting X before the nvidia kernel module is ready to run.
- 
- NOTE WELL--the original reporter had the problem that his system was starting on tty7 and others were discussing tty1 starts here as well. At comment 30
- the problem was split with regard to tty1/tty7 starts and tty7 discussion moved to #626723. See original description below for his original report.
+ 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.

** Package changed: plymouth (Ubuntu Maverick) => gdm (Ubuntu Maverick)

** Package changed: xserver-xorg-video-ati (Ubuntu Maverick) => nvidia-
graphics-drivers (Ubuntu Maverick)

** Changed in: nvidia-graphics-drivers (Ubuntu Maverick)
       Status: Invalid => Confirmed

** Also affects: gdm (Ubuntu Lucid)
   Importance: Undecided
       Status: New

** Also affects: nvidia-graphics-drivers (Ubuntu Lucid)
   Importance: Undecided
       Status: New

** Description changed:

  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.

** Tags added: lucid
** Tags 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

-- 
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.