Hi,

This problem began when I upgraded to Slackware 12.0. Once in a while, Konqueror freezes. If I try to kill the application and start it again, the GUI is still unresponsive. I have to log out from KDE and then log in again.

Some more clues:
- It's only the file manager that freezes - I can still use Konqueror as a web browser.
- When Konqueror freezes for my user, I can still run it as another user.
- It seems to have something to do with "Icon View" (which is my preferred mode).
- I thought it had something to do with my external harddrive first. But right now I don't have it mounted, but Konqueror still froze.
- I don't really know how to reproduce this behaviour; it seems to happen randomly.
- I use Slackware 12.0, KDE 3.5.7 (included in distro) and Konqueror 3.5.7 (included).

I don't even know where to start looking for problems. Hope someone has a nice solution.

Thanks in advance.

Had same problem, and it had to do with the old .kde, .kderc files. Did not find the specific culprit, but I noticed it had to do with the DCOP server Klauncher uses to communicate.

Below are the steps I took to fix the problem (from an instructional p.o.v.):

- Change to root
- Change runlevel to 3 (# init 3)
- Log back in as root if there is no longer an active login
- Go to your affected user's home directory (# cd ~<affected_user>).
- Either:
delete the old .kde, .kderc files (# rm -f .kde .kderc), or
rename the old .kde, .kderc files to some other name for
backup purposes (# mv .kde kde.orig; mv .kderc kderc.orig).
- restart x by switching back to runlevel 4 (# init 4)
- log back onto KDE as the affected user to have it create new default files.

Once I had KDE recreate all its default files, the problem went away.

Hope it works with you.

GL

Thanks for your answer. I suspected that it had something to do with old configuration files. I'm pretty sure your solution will fix it; however, I don't really like the idea of having all my configuration erased (of course I can backup it, but it still requires some time to fix it).

So if there's somebody who knows which files(s) I have to delete (and not my entire .kde), please tell me. Otherwise I think I'll wait until I upgrade to KDE4.

I thought I would let you know I restored my previous .kde directory and .kderc file after KDE re-created everything, and now klauncher seems to be working fine. Which leads me to believe the problem may have been due to the cache left over from the previous KDE version..

One thing you may try, would be to wipe out kde's caching, and have it re-create it. You could do the following:

- log out out kde
- hit ctrl+alt+f6 to switch out of Xorg (switching to virtual console 6)
- log in as the affected user.
- remove the ~/.DCOPserver_<hostname>_* file and link
- go into the affected user's .kde directory.
- remove the cache-<hostname> link, the socket-<hostname> link, the tmp-<hostname> link, the /var/tmp/kdecache-<affected_user_name> directory, /tmp/ksocket-<affected_user_name> directory, and the /tmp/kde-<affected_user_name> directory.
- log out. and hit alt+f7. (switching back to Xorg)
- log back onto kde to have kde re-create the caching and file(s).

Give the above a try as it should not affect any of your settings, but as a precaution, you may want to make a backup just in case.

GL