LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 05-08-2004, 03:31 AM   #1
gonzalo76
Member
 
Registered: Feb 2004
Location: Argentina
Distribution: Fedora Core
Posts: 34

Rep: Reputation: 15
KDE error: Could not start kdeinit...


Hi,

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?

Greetings
gonzalo
 
Old 05-08-2004, 05:34 AM   #2
thegeekster
Member
 
Registered: Dec 2003
Location: USA (Pacific coast)
Distribution: Vector 5.8-SOHO, FreeBSD 6.2
Posts: 513

Rep: Reputation: 33
A search here turned up this thread:

http://www.linuxquestions.org/questi...hreadid=126525


and a Google search turned up this thread:

http://www.linuxforum.com/forums/ind...showtopic=8053

The first one is about permissions problems in the user's home directory and the second one is about missing libraries

HTH
---thegeekster
 
Old 05-08-2004, 09:59 AM   #3
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
I got the following snippet from the kde site, and have used it with success on several occaisions:

***************************************************************

4.17.

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.

*************************************************************

tobyl
 
Old 05-08-2004, 01:26 PM   #4
gonzalo76
Member
 
Registered: Feb 2004
Location: Argentina
Distribution: Fedora Core
Posts: 34

Original Poster
Rep: Reputation: 15
Thank you for your replies:

tobyl:

Actually, I don't have any ~/.DCOPserver folder. Is this correct?
 
Old 05-09-2004, 09:47 AM   #5
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
Yes, this is correct.
But I would expect you to have two files, (not folders)

Mine looks like

/home/toby/.DCOPserver_darkstar__:0
/home/toby/.DCOPserver_darkstar__0

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.

tobyl

Last edited by tobyl; 05-09-2004 at 09:52 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Could not start kdeinit - KDE won't run slackware_10_1 Linux - Software 5 06-29-2005 04:12 PM
KDE error -- Could not start kdeinit. Check your installation. Dade Slackware 18 11-27-2004 08:07 PM
KDE 3.1 startup message: 'Could not start kdeinit' -- what does this mean? nimcha Linux - Software 5 06-16-2004 04:43 PM
KDE won't start. On log in kdeinit error bdika Linux - Software 6 11-10-2003 08:19 PM
can not start kdeinit error johnva Linux - Software 1 07-13-2003 04:36 AM


All times are GMT -5. The time now is 02:25 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration