Yet another weirdness on my desktops (xorg-7.3, gnome-2.20.latest and specifically xorg-server-1.4.0 and gdm-2.20.1). Once I've got gdm built, I switch my default runlevel to 5. Normally, it "just works", but on current builds I'm seeing a rather weird shutdown process:
log out, X restarts and gdm appears from gdm, select the option to shut down and confirm it. What used to happen was a switch back to tty1 with the console messages as X was killed and everything shut down. What happens now is: 1. gdm calls 'shutdown -h now', causing the rc bootscript to be called for runlevel 0. 2. The Knn scripts run - in my case, starting with cups 3. X restarts (in my opinion, this is not the expected behaviour). (in the log, the kernel agp messages appear) 4. My second Knn script is gdm - at this point X hasn't finished reloading so the test for /var/run/gdm.pid fails and gdm-stop is not called (even if the test was removed, gdm-stop has the same test and there is, as yet, nothing to kill). 5. My third Knn script is for fcron - this reports sigterm 6. the [drm] messages appear (setting the GART location, loading R200 Microcode, etc and at this point X has restarted and gdm appears. I can login, but the shutdown is proceding and eventually gdm gets killed by the sendsignals script and I can see the console messages. I'm way out of my depth in trying to understand how modular X fits together, but does it seem likely that this is a bug, or a deliberate change, in xorg-server or am I looking at the wrong package ? Anybody else seeing anything similar ? Is it in fact a change in gdm ? ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
