Logout problem

[MechCD]

Today i woke up and saw that i was logged out........ I left it running Ghclient as mechcd the night before.... So I rebooted just for kicks logged in (got to desktop) and after about 2 seconds a black screen flashes by and I'm back at the login prompt (graphical login) I logged back in, and I'm still running for the moment. What could be causing this?

Also, when I do a Ctrl-Alt-f1 i can't get back to X and gnome.

[dnar]

Arggggg! I had a nice reply here for you before my ISP dropped out!!!!!!!

Ok, forst off, you don't really need to reboot Linux, even is things go a miss.... Simply kill/respawn the daemon or task in question. Remeber, this is a REAL operating system.

If X is behaving badly, you have several methods to restart the X engine, but first always close down Gnome or KDE and return to the graphical login, then open a text cosole (Ctl-Alt-F1) and do either of the following:

1. Change the runlevel to multiuser no X - "telinit 3" and then back to multiuser with X - "telinit 5". X-Windows will do a complete restart.
2. Kill off X like so: "killall X". XFree86 will restart by itself.
3. Kill off the Gnome login manager - "killall gdm". The login manager will also restart by itself.

These "daemons" that restart automatically are actually controlled by the kernel, and are defined in "/etc/inittab". If you have a look, you will see 6 x "mingetty" daemons, each of those is your console logins. The xdm is the graphical login daemon, and is actually one of any 3rd party daemons, in your case "gdm" or the Gnome login daemon. Now these daemons you will see are "respawn" defined, that is, when they die the kernel will ensure another is recreated. Neat. That is kind of esential, otherwise you would not have a login prompt when you close X or a a console.

As for X crashing, it can happen, I have a very stabe environment now since going to XFree86 4.0.3 and the latest (beta) matrox dual-head drivers.

If you check the logfile "/var/log/XFree86.0.log" you may get an indication of the problem.... I have also in the past seen X crashes when the OpenGL screensavers run, on less than brilliand video cards (SiS chipsets, Permedia chipsets) and I have seen many reports also with Nvidia cards too.

[MechCD]

Okey dokey

[MechCD]

Originally posted by dnar
Arggggg! I had a nice reply here for you before my ISP dropped out!!!!!!!

Ok, forst off, you don't really need to reboot Linux, even is things go a miss.... Simply kill/respawn the daemon or task in question. Remeber, this is a REAL operating system.

If X is behaving badly, you have several methods to restart the X engine, but first always close down Gnome or KDE and return to the graphical login, then open a text cosole (Ctl-Alt-F1) and do either of the following:

1. Change the runlevel to multiuser no X - "telinit 3" and then back to multiuser with X - "telinit 5". X-Windows will do a complete restart.
2. Kill off X like so: "killall X". XFree86 will restart by itself.
3. Kill off the Gnome login manager - "killall gdm". The login manager will also restart by itself.

These "daemons" that restart automatically are actually controlled by the kernel, and are defined in "/etc/inittab". If you have a look, you will see 6 x "mingetty" daemons, each of those is your console logins. The xdm is the graphical login daemon, and is actually one of any 3rd party daemons, in your case "gdm" or the Gnome login daemon. Now these daemons you will see are "respawn" defined, that is, when they die the kernel will ensure another is recreated. Neat. That is kind of esential, otherwise you would not have a login prompt when you close X or a a console.

As for X crashing, it can happen, I have a very stabe environment now since going to XFree86 4.0.3 and the latest (beta) matrox dual-head drivers.

If you check the logfile "/var/log/XFree86.0.log" you may get an indication of the problem.... I have also in the past seen X crashes when the OpenGL screensavers run, on less than brilliand video cards (SiS chipsets, Permedia chipsets) and I have seen many reports also with Nvidia cards too.

Ok, that all works and makes sense, but what about ctrl-Alt- F1?

I tried Ctrl-alt-F7 , but can't get back........................ I'm tryin' to run g@h without havin' to worry about login and logouts cuz I switch sometimes mid unit :eek:

Wouldn't a telinit 3 kill g@h?

[dnar]

Originally posted by MechCD




Ok, that all works and makes sense, but what about ctrl-Alt- F1?



I tried Ctrl-alt-F7 , but can't get back........................ I'm tryin' to run g@h without havin' to worry about login and logouts cuz I switch sometimes mid unit :eek:



Wouldn't a telinit 3 kill g@h?

Maybe it's Ctl-Alt-F8 for you....

No, going to runlevel 3 should not kill a client running on Console F1....

[MechCD]

Originally posted by dnar










Maybe it's Ctl-Alt-F8 for you....







No, going to runlevel 3 should not kill a client running on Console F1....





Actually it would. I would ctrl-alt-f1, run gh, and then ic an't get another login screen! i would have to ctrl-c gh to get back to a console :( Somethin' screwy goin' on here:confused: :mad:

[dnar]

Mmmmm. I just did exactly that, and no prob's... Back to X, back to F1, back again.....

What happens if you launch the client as a background task:

./ghclient.x &

and then try....

[MechCD]

Originally posted by dnar
Mmmmm. I just did exactly that, and no prob's... Back to X, back to F1, back again.....



What happens if you launch the client as a background task:



./ghclient.x &



and then try....

Ok, I'm logged in as mechcd in X from the graphical login. I hit ctrl-alt-F1 and it goes to a text login. i login as mechcd. I hit ctrl-alt-f8 or f7 and nothing happens. i've tried from F1 to F12 and it just won't go back.

I'll try that backround task idea, it stays logged in after a telinit 3 or a daemon restart

[dnar]

That is really weird...

Oh course you stay logged in between runlevel 5 -> 3 chage..... All that happens is the "K" scripts/daemons in /etc/rc.d/rc5.d get killed and the "S" scripts/daemons in /etc/rc.d/rc3.d get started....