You are not logged in.
Pages: 1
Hi all!
I boot directly to KDE using kdm as a deamon.
I login as a normal user.
Everything works fine but when I logout from KDE instead of going to KDE Welcome Login screen I'm presented with console login. (user is loged out)
However kdm has not been terminated because if I login to console as root and give /etc/rc.d kdm start I get [FAIL].
So I have to give /etc/rc.d/kdm stop which is a [DONE] and then /etc/rc.d/kdm start again to start KDE.
If I logout again then instead of console login that I said before I'm thrown at root's prompt which I used to start KDE.
Can anyone imagine what could be the problem?
Thanks a lot!
Offline
When you log out and are presented with the console login screen, does KDM come back if you do Alt+F7?
Also, check /var/log/daemon.log for anything suspicious.
And welcome to the boards ![]()
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
When you log out and are presented with the console login screen, does KDM come back if you do Alt+F7?
Also, check /var/log/daemon.log for anything suspicious.And welcome to the boards
Thanks for replying!
No, ALt+F7 does not bring back kdm.
I just tried ''End current session'' now and the last lines in /var/log/daemon.log are:
Sep 9 14:40:40 Pumbu kdm: :0[4283]: IO Error in XOpenDisplay
Sep 9 14:40:40 Pumbu kdm[2849]: Display :0 cannot be opened
Sep 9 14:40:40 Pumbu kdm[2849]: Unable to fire up local display :0; disabling.Does it look like an error with my xorg.conf file?
thanks
Offline
If it was a problem with your xorg.conf, then KDM wouldn't start in the first place. It is likely to be an KDM config problem. I suppose go through /opt/kde/share/config/kdm/ and look for anything suspicious... Although I don't know what suspicious actually is, so I think you should hope someone else can help you out a bit more ![]()
On a side note, things that you could check are that the "lo" network device is configured properly, and that iptables (or similar) isn't blocking anything. But these are kinda shots-in-the-dark..
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
Pages: 1