Bug#687569: gdm3 displays "Oh No! Something has gone wrong"

Felix Koop fdp at fkoop.de
Tue Oct 22 21:52:20 UTC 2013

I was still seeing it until a few weeks ago. At that time I deleted
several files and directories in my home directory. After that action, I
did not see this behaviour any longer. So it must have been some config
information in a file in the home directory. Unfortunately I do not have
a copy of the files I deleted and cannot test this any more.

Am Freitag, den 18.10.2013, 15:30 +0200 schrieb intrigeri: 
> Hi Felix,
> Josselin Mouette wrote (28 Sep 2012 19:05:25 GMT) :
> > Le vendredi 28 septembre 2012 à 09:12 +0200, Andreas Beckmann a écrit : 
> >> 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 :-)
> > Felix, can you try these versions?
> >> 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.
> > This bug should have been fixed in GDM 3.4. Are you still seeing it?
> Ping?
> Cheers,
> --
>   intrigeri
>   | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
>   | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc

Mit freundlichen Grüßen

Felix Koop

More information about the pkg-nvidia-devel mailing list