KDE screwed? DCOPServer trouble
 

I hope someone can help me with this. I usually use Fluxbox as my WM, but occasionally I use KDE, when I stumble upon something my CLI abilities aren't sufficient for. This switching has made KDE-related applications behave... strangely. I searched for this issue here, and others seem to have encountered it, but I couldn't find a useable answer to it.I wouldn't want to be without the 4 appplications K3B, Kaffeine, Juk and, occasionally, Konqueror.
When I try running one of the programs, I get this:

* * *
[mjj@localhost mjj]$ juk
/usr/bin/X11/iceauth: timeout in locking authority file /home/mjj/.ICEauthority
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failedICE Connection rejected!

DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
DCOPServer self-test failed.
ICE Connection rejected!

sh: line 1: iceauth: command not found
kdeinit: DCOPServer could not be started, aborting.
juk: ERROR: KUniqueApplication: Can't setup DCOP communication.
[mjj@localhost mjj]$

* * *

Now, I don't have a clue as to how this has happened - or how to set it straight! I have always been able to iron out issues in the past - but this one has me baffled.
Please help me, if someone has encountered the problem and beaten it.

"/usr/bin/X11/iceauth: timeout in locking authority file /home/mjj/.ICEauthority
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failedICE Connection rejected!"

It has been several years since I had this problem (which developed when I first tried to convert from KDE 2 to KDE 3) so I am vague about the details of the solution. When KDE starts it sets up a correspondence between some files in /home/user and /tmp. When KDE ends it removes the correspondence between the two sets of files. I think that your problem has to do with the correspondence going awry and being permanently out of sync. The files on my KDE system that I am talking about are:
/home/user/.DCOPserver_linux__0
/home/user/.DCOPserver_linux_:0
/home/user/.ICEauthority
The files contained in directory: /tmp/ksocket-user
The files contained in directory: /tmp/mcop-user
The files contained in directory: /tmp/orbit-user

Under different circumstances I remember three different solutions to the problem:

1. Log in as root and delete every file and directory in /tmp which contains user in its name. Then log into user.

2. If 1. doesn't work then try creating a user with a new name and abandon the screwed up user name.

3. Once somebody asked a similar question here on LinuxQuestions and the problem turned out to be that he had a mixture of KDE releases, 3.1.2 and 3.1.3 or something like that. Once he got every KDE package to the latest release the problem disappeared. Take a look at your KDE versions with:

rpm -qa | sort | less

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Try checking you've not turned off your lo interface via the Network service in the MCC. I think that helped when I had this problem a while back with 9.1.

Can't get the lame-ass crap to work.

I had the same problem.

I deleted
home/user/.DCOPserver_linux__0
/home/user/.DCOPserver_linux_:0
/home/user/.ICEauthority

which did not help, and as root I wiped out the /tmp directory which DID help. <RELIEF>
No lost settings, no different users or whatever.

I still wonder what has caused this problem. Suddenly it took a long time (3-4 minutes) before KDE applications would launch. When trying to restart KDE (and I even rebooted Linux) the problem occured.

Thanks to you who posted a solution here or in other threads.

jlinkels

the thing i posted was bogus so i removed

I had that same problem on installation of the SESarge PAM runtimes.

Deleting those three files in my home directory was enough to make it go away.