Cliff Sarginson wrote:
On Tue, Oct 30, 2001 at 10:16:09PM +0100, David List wrote:
I have recently installed SuSE Linux 7.3 Professional on a system, which now behaves in a manner that I have never seen before: When the system has booted, I can log in through kdm and out again as any user on the system. If I switch to any of the virtual consoles tty1 through tty6 I can log in, but as soon as I log out again, I get a blank monitor. Trying to switch between virtual consoles or back to tty7 where X resides does nothing for me. The power-LED on the monitor is still green. The monitor's power-LED is amber if the monitor lacks signal or is in suspend-mode. The system has APM disabled, so that's not disturbing.
What can this be?
It's a "feature"....read on. :-) I just installed an S3 Savage 32 meg AGP video card and it gives similar behavior. On my prior system, I could hit control-alt-backspace to quickly exit X with no problem. Now, if any X apps are running and I hit the combo, I get the exact same symptoms as you, necesitating a reboot. I encounter no problem if I hit "exit" on my fvwm2 menu. Upon closer examination of the .fvwmrc file, the control-alt-backspace calls the function "Quit and save"; while the Exit button simply calls Quit. Upon looking at the console message when the problem occurs, it says something like " waiting for X server to close" --when it hangs. If I politely exit X, with the appropriate "quit button", it just says "connection to X server shut down, with no problem. So......it looks like the problem is the function used to exit X. YMMV depending on which window manager you have, but I'll bet the problem is similar. I look at it as a "feature", ;-). I was always wondering what could be done about the "insecure Xlock and Xscreensaver" problem, which would allow someone at the console, to bypass the X-screensaver lock, by hitting control-alt-backspace. The way my video works now, if someone does try to bypass my X-screensaver, it locks the system up, and a reboot just presents logon prompts. So maybe this "glitch" can be incorporated into everyone's system. to improve X-security. :-)