On 2012-09-28 00:14, Josselin Mouette wrote: > Le mercredi 26 septembre 2012 à 23:41 +0200, Felix Koop a écrit : >> server glx vendor string: NVIDIA Corporation > >> But what I do not understand is, that it worked until about 2 or 3 weeks >> ago. And there was no modification in gnome-shell at that time. > > Uh oh, indeed that coincides with an upgrade of Nvidia drivers to > 304.48. > > If the latest version is not compatible with gnome-shell, that’s a big > problem. > CCing Nvidia maintainers for more information.
There is 304.51 in experimental and everything < 304.48 in snapshots. Please try these and if it's not working in .51 find the first broken one. If it still seems related to nvidia, report a new bug against nvidia-glx (using the experimental version) with reportbug to collect system information and logfiles. This may also be done from the console after you got the error from gdm. Then I'll give you instructions how to forward this to Nvidia, they have become more responsive recently :-) What I see in many bug reports against nvidia, is that gdm3 tends to go havoc and spawns hundreds of X servers if something goes wrong. Leaving you many many Xorg.*.log[.old]. I experienced this myself by e.g. just not having a display connected. Filed/commented, but I'm too lazy to look up the bug numbers right now. Worked around by s/gdm3/kdm/, sorry. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
