You are not logged in.

1

Saturday, February 21st 2004, 11:17am

Locked out of KDE, help!

My system crashed while I was in a KDE session, requiring fsck at reboot. Now I can't start KDE (version 3.2) with the same user account I was using at the time of the crash. :cry: I get the ksplash window, but the progress bar sticks at the second step for a while, then the splash window disappears and I get left with a blank X root window with no functions except Ctrl-Alt-Backspace working.
The last message in .xsession-errors afterwards is: "kbuildsycoca running..."
Other user accounts (root and one new account I created) can use KDE just fine, so I believe some of the KDE startup files in my home directory must be trashed. However, I tried removing the .kde directory and .kderc but that didn't help. What other files does KDE 3.2 use during the start? What's "kbuildsycoca" and what could cause it to lock up?
The OS is Fedora Core 2 Test 1 with latest updates.

2

Saturday, February 21st 2004, 1:16pm

Re:Locked out of KDE, help!

Check up if the following directories are present
/tmp/kde-$USER and /tmp/ksocket-$USER.
delete them if they are present and try again.
If you are still not able to login , select "failsafe terminal" in gdm login screen and try running the command "kbuildsycoca" and see if it exits properly without any error messages.

3

Saturday, February 21st 2004, 2:17pm

Removing the files from /tmp didn't help. Running ksyscoca gives:[code:1]$ kbuildsycoca
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
Warning: kbuildsycoca is unable to register with DCOP.
kbuildsycoca running...
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
kbuildsycoca running...
[/code:1] and then nothing. It appears to be stuck in a loop using all CPU:[code:1]$ top -b -n 1
top - 16:18:50 up 7 min, 3 users, load average: 1.05, 0.66, 0.30
Tasks: 58 total, 2 running, 56 sleeping, 0 stopped, 0 zombie
Cpu(s): 56.4% us, 2.2% sy, 0.0% ni, 33.8% id, 7.6% wa, 0.1% hi, 0.0% si
Mem: 515832k total, 271324k used, 244508k free, 14736k buffers
Swap: 1052216k total, 0k used, 1052216k free, 161840k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1739 mk 25 0 23532 8300 22m R 99.0 1.6 3:52.74 kdeinit
(...)
$ ps x
PID TTY STAT TIME COMMAND
1728 pts/2 S 0:00 kbuildsycoca
1729 pts/2 S 0:00 /usr/bin/kdeinit --suicide
1730 ? S 0:00 kdeinit: Starting up...
1733 ? S 0:00 kdeinit: dcopserver --nosid --suicide
1735 ? S 0:00 kdeinit: klauncher
1736 ? S 0:00 kdeinit: kded
1737 ? S 0:00 kdeinit: kded
1739 ? R 4:48 kdeinit: kbuildsycoca --incremental --checkstamps
[/code:1]

4

Saturday, February 21st 2004, 11:37pm

Sorry to not mention this on the last reply
you have to remove /var/tmp/kdecache-$USER too. this is where kbuildsycoca stores its cache.

checking the ps output shows that two kbuildsycoca processes are running. try this.
remove the above directory and also directories in /tmp. delete .kde directory. check ps to see if any kde processes are running, terminate them. and then try to login.

5

Sunday, February 22nd 2004, 12:43am

Now it works again :D :D :D
Many thanks!