SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Last night I tried to upgrade my previous KDE verstion to the new one 3.2.2.
But when I tried to log in into KDE, two error messages appeared:
Quote:
Could not start kdeinit. Check your installation.
Quote:
DCOP communications error (The KDE Session Manager)
There was an error setting up inter-process
communications for KDE. The message returned
bu the system was:
Could not read network connection list.
/home/gonzalo/.DCOPserver_pc-gonzalo_0
Please check that the "dcopserver" program is running!
Does anybody know how to fix this in order to log in into KDE session?
I upgraded KDE and it seemed to go fine, but when I start it, I get a blank grey screen, and nothing happens. There are errors in the console about DCOPserver. What's going on?
KDE uses several temporary files during it's operation. These are usually to be found in the following locations:
*
~/.DCOPserver-* (there are usually two of these, one is a symlink to the other)
*
~/.kde/socket-hostname
*
~/.kde/tmp-hostname which is normally a symlink to the next file:
*
/tmp/tmp-kde-USER
*
~/.kde/socket-hostname which is also normally a symlink to:
*
/tmp/ksocket-USER
If the symlinks get broken, usually because a cron or shutdown script is emptying out the /tmp directory, then strange things will happen. These files, and the symlinks, will all be created automatically at the start of KDE so you can safely remove them while KDE is not running.
If you are getting only a grey screen when you start KDE, or if you get an error message telling you to Check your installation, then shut down X and delete all the files listed above, then try to restart X.
the first is a symlink to the second
delete these, likewise in root folder.
In /home/user/.kde delete
socket-hostname
tmp-hostname
these are symlinks to the folders in /tmp
likewise for root
In /tmp delete folders
kde-root
kde-yourusername
ksocket-root
ksocket-yourusername
(yes, the layout has changed slightly from my post, sorry I did not notice)
delete these without kde running if you can, don't forget you will need to do a [recursive] rm -r kde-root etc if you do it from the console on folders as a straight rm will just tell you that it is a directory.
***PLEASE BE VERY CAREFUL USING rm -r , ESPECIALLY AS ROOT !!!***
YOU COULD DO A LOT OF DAMAGE TO YOUR SYSTEM, AVOID WILDCARDS (*)!!!
When you restart kde, these files and folders (why am I saying folders? sounds awfully M$oft, I mean directories!) will be recreated and all will be well again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.