You are not logged in.
I did the update yesterday morning. Now when the login window comes up KDE loads very slowly to a plain white screen with several small red boxes with X's scattered across the top. It continues to load as the SpiderOak banner comes up and the sound initializes but I'm unable to do anything short of a power-down.
Doing a "grep EE /var/log/Xorg.o.log" returns
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[18.727] (II) Loading extension MIT-SCREEN-SAVER
MIT-SCREEN-SAVER seems to be related to xscreensaver, which I tried installing to no effect.
Help?
Last edited by cylverbak (2011-07-08 23:46:17)
Offline
Is there anything interesting in your ~/.xsession-errors log?
Offline
a). create a new user then log into KDE as that user.
b). or, mv ~/.kde4 ~/kde4, then log into KDE with empty settings.
If either way works well, it means the problem lies in your config files under ~/.kde4.
Offline
Oh and btw cylverbak the reason that the MIT-SCREEN-SAVER line came up in your grep is because of the EE in SCREEN, the (II) after the timestamp shows that the line is informational, not an error which would have (EE) after the timestamp, e.g.
[ 58.291] (EE) Failed to load module "fbdev" (module does not exist, 0)
Offline
Thanks for the replies.
@ George: xsession? corrupt KSycoca database kind of stands out but there's a lot more that I don't know how to interpret. Maybe I'll start a live session and post the last attempt to see if it means anything to you. And thanks for that information on MIT-SCREEN-SAVER.
@ adaptee: created a new user and logged in and was logged out and back at the login screen in a matter of seconds.
renamed .kde4 to kde4. Got rid of the red squares with the X's. Now I've got a pretty white screen and a black mouse pointer. Dead in the water ![]()
I probably should see what the pacman log has to say too. I was away from the computer while it was upgrading but it didn't generate any error messages. . .
Edit: pacman.log shows updates went smoothly. I can post the appropriate section if that would help.
Last edited by cylverbak (2011-07-08 23:16:40)
Offline
<downcast look> root partition was full! Emptied the cache and things are working again. Now I have to figure out why it filled and how to resize partitions without losing stuff. I've got 2 SSD's partitoned with GPT. Sorry for wasting your time. Learned more about linux (again the hard way!).
Thanks again for your support. I appreciate it.
Offline