Dear maintainers, this bug is NOT a problem of nvidia-glx! I also tested with driver "nv", and got the same result. Please take a look at my last message. IMO there might be several possible packages involved:
1. the kernel itself 2. udev 3. xserver-xorg 4. maybe some relationships to the "nouveau" kernel-module in the kernel, although blacklisting as well as deleting this module showed also no success. Due to my tests, the following packages can be excluded, as I installed formerly working versions or deinstalled them also without success: 1. kdm, gdm and xdm 2, nvidia-glx and nvidia-kernel 3. synaptics-driver 4. evdev-driver I suppose, the problem might be somewhere in the start sequence or in xserver- xorg, while starting the FIRST time (and checking the hardware). This could explain, why either restarting kdm or changing runlevel from 2 to 1 and back to 2 (so that all startscreipts are executed again) is working without any errors. Meanwhile I updated my second computer from testing to sid, and it shos the same behaviour there. This proves, it not only a 64-bit problem, but a general problem. I hope this might help a little bit. Best regards Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
