Xorg cannot start when starting it for the second time (or at least when logging out from a gdm session). It shows a black screen with a cursor in the upper left corner, and tries about three times to change the resolution before reporting Temporary workaround is to downgrade to nvidia-drivers-180.60. Reproducible: Always Steps to Reproduce: Log out of a gdm session. The bug occured on a Thinkpad T61 with a Nvidia Quadro NVS 140M. In order to enter suspend to ram, I use the following bios quirks: power_management.quirk.s3_mode = true power_management.quirk.s3_bios = false power_management.quirk.save_pci = true power_management.quirk.vbemode_restore = true
How exactly did you cause this to happen? I've got the same laptop with the same card and I can't reproduce.
It happens every time I run gnome-session-save --logout. How can I debug it further? Model: Thinkpad T61 64576DU /var/log/Xorg.0.log shows nothing that weren't there when using 180.60. emerge --info: Portage 2.1.6.13 (default/linux/amd64/10.0/desktop, gcc-4.3.4, glibc-2.9_p20081201-r2, 2.6.28-tuxonice-r10 x86_64) ================================================================= System uname: Linux-2.6.28-tuxonice-r10-x86_64-Intel-R-_Core-TM-2_Duo_CPU_T7500_@_2.20GHz-with-gentoo-1.12.13 Timestamp of tree: Sat, 12 Dec 2009 13:45:02 +0000 ccache version 2.4 [enabled] app-shells/bash: 4.0_p35 dev-java/java-config: 2.1.9-r1 dev-lang/python: 2.6.4 dev-util/ccache: 2.4-r7 dev-util/cmake: 2.6.4-r3 sys-apps/baselayout: 1.12.13 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6b virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=core2 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-march=core2 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch userpriv usersandbox" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo" LANG="en_US" LDFLAGS="-Wl,-O1" LINGUAS="en da" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="..." ELIBC="glibc" FOO2ZJS_DEVICES="km2430" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en da" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="nvidia nv"
Can you run anything other than a Gnome session? Can you use the basic X session with twm?
Also, how about attaching your Xorg log from 1st good attempt and 2nd failed attempt?
Created attachment 214927 [details] Xorg.0.log for a gdm session before logging out
Created attachment 214929 [details] Xorg.0.log for a gdm session after logging out Note that the log ends when loading the GLX extension.
Starting a plain X server using the commands X & DISPLAY=":0" xterm works fine but takes a long time before showing up.
I just tried using xdm. It is able display the login screen after logging out of the first session, but fails when trying to start the second login session, leaving the following in .xsession-errors: XDM authorization key matches an existing client! ** (gnome-session:5409): WARNING **: Cannot open display:
You are getting some weird symptoms from that driver... please post the log from your plain X session too, in case it has any clues.
Created attachment 215216 [details] Xorg.0.log for a plain X session
I did see one interesting difference between your logs, aside from starting up normally vs. getting stuck at GLX init: the failed attempt was trying to come up on vt 8 instead of vt 7 like the other two. Not sure if that's a relevant clue or not. I haven't been able to find any other complaints like yours; might be the combination of this driver version with the tuxonice kernel you're using. Turning this over to our Nvidia maintainers, including Doug who has a match for your hardware...
I think I have the same issue with x11-drivers/nvidia-drivers-173.14.25 on top of x11-base/xorg-server-1.7.6 (full ~amd64) The very same driver works fine with x11-base/xorg-server-1.6.5-r1 (amd64 with some ~amd64 exceptions, but not within nvidia/Xorg dependency subtree) Hardware: GeForce FX5200
I investigated the problem a little further: The failure occurs only when using gdm. After logging out the first time, I can start both xdm and slim without problems. Also, when there is already an X session running on VT7, and I start gdm, gdm offers to start on VT8, which surprisingly works.
(In reply to comment #13) > I investigated the problem a little further: > > The failure occurs only when using gdm. After logging out the first time, I > can start both xdm and slim without problems. Also, when there is already an > X session running on VT7, and I start gdm, gdm offers to start on VT8, which > surprisingly works. I guess it was a bad GDM interaction. Unfortunately this bug appears to have gotten stale due to slipping between the cracks. Please retest with the latest versions and all should be well.
