Bug#604953: gdm3: Crash on launching GDM3 user-selection

[Daniel Golesny]

> I don't think this is a NVIDIA problem. Please try to get your system back 
> into the state before running nvidia-xconfig, e..g move /etc/X11/xorg.conf 

You're right, after deleting the xorg.conf I could start my system two 
times (with poor resolution), but after these two times, I couldn't 
bring up the system the last 10 tries anymore.
Before the todays update I could start it with "init 2" from recovery 
mode. Now I can't start my system anymore.

> squeeze install. Try to reproduce the original problem and 
> attach /var/log/Xorg.0.log and the logfile from gdm3 (sorry, I don't know 
> where to find this) to this bug. You'll have to save the logs while in 
> recovery mode, otherwise they get overwritten at the next restart.

I deleted most logfiles including XOrg, GDM3-directory, ... and after 
the reboot I had only some empty log files:
   /var/log/Xorg.0.log
   /var/log/gdm3/:0-slave.log
   /var/log/gdm3/:0.log
   /var/log/kern.log

But I've found an error message in the syslog.1
I think this is not an gdm3-bug its an kernel bug.

Nov 29 18:04:09 venus kernel: [   23.356256] BUG: unable to handle 
kernel NULL pointer dereference at (null)

I've attached the syslog. Can you confirm this?
Can you move the bug to the correct module? Or should I create a new 
one? Which is the correct module?
I'm new in this process ... Tell me, if you need more information.


Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syslog.1.gz
Type: application/x-gzip
Size: 33654 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20101129/2456afe6/attachment-0001.bin>