You are not logged in.
Every time I log out of my KDE session, I get kicked over to the (vc/1) terminal, rather than back to a KDM login screen. Is this a common trait of Arch or is something not working right? I'd rather like to see a KDM screen.
I'm currently using the inittab method of loading KDM, however it happens with the daemon method as well.
If I jump back to tty7 after I log out, all I see is a blinking cursor and my whole system freezes, forcing a hard reset.
Any suggestions? Thanks
Last edited by thayer.w (2007-06-01 19:21:28)
thayer williams ~ cinderwick.ca
Offline
I have the same problem. Haven't been able to come up with a solution yet.
Offline
I think it has something to do with the xorg.conf. Do you by chance have an ATI graphics card?
If I find a solution, I'll be sure to post it to this thread.
thayer williams ~ cinderwick.ca
Offline
Yes, ATI X1300.
Offline
I figured as much. It's definitely related to the fglrx ATI driver. When I revert back to the default VESA driver it fixes KDM. Of course, I'm not about to use 1024x768 when it's supposed to run at 1680x1050.
thayer williams ~ cinderwick.ca
Offline
I'm using fglrx and I can log out and get my login screen back. I'm using SLiM instead of KDM, though, so I'm not sure how useful this is to you.
I do know that fglrx screws me up like you're describing if I use two monitors, though. It has some real problems with multihead.
Offline
Found it!
Edit as root:
/opt/kde/share/config/kdm/kdmrc
add:
TerminateServer=true
under the section [X-*-Core]
For example:
[X-*-Core]
AllowNullPasswd=false
AllowRootLogin=false
AllowShutdown=Root
Authorize=true
AutoReLogin=false
ClientLogFile=.xsession-errors-%s
FailsafeClient=/usr/bin/xterm
Reset=/opt/kde/share/config/kdm/Xreset
Resources=/opt/kde/share/config/kdm/Xresources
ServerCmd=/usr/bin/X -br
Session=/opt/kde/share/config/kdm/Xsession
SessionsDirs=/etc/X11/sessions,/usr/share/xsessions,/opt/kde/share/apps/kdm/sessions
Setup=/opt/kde/share/config/kdm/Xsetup
Startup=/opt/kde/share/config/kdm/Xstartup
TerminateServer=true
Xrdb=/usr/bin/xrdb
It's no solution, but it's a good workaround. I'm guessing the true solution lies somewhere in ATI's proprietary driver, and it's anyone's guess if it will ever be addressed.
Last edited by thayer.w (2007-06-01 19:09:12)
thayer williams ~ cinderwick.ca
Offline
I have no idea how you found it, but it works! Thanks for solving it yourself, hehe.
Offline
I remembered doing something similar with GDM when I was running Ubuntu... Google is king.
The relevant bits have been added to the Troubleshooting section of the ATI Radeon Wiki for future reference.
Last edited by thayer.w (2007-06-01 22:12:36)
thayer williams ~ cinderwick.ca
Offline