Comment 21 for bug 64735

Same problem here in Kubuntu Feisty

'rm /tmp/.X0-lock' does'nt make a difference

The issue i have only happens when i startup kate the first time in Konsole after booting into Kubuntu, after that the only error i receive is 'QObject::disconnect: Unexpected null parameter' on exit - which by the way 'rm /tmp/.X0-lock' seemed to remove only during that session though?

Once in a while i might receive this:

$ sudo kate myfile.txt
DCOPClient::attachInternal. Attach failed Could not open network socket
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /root/.DCOPserver_typhoonx-desktop__0
and start dcopserver again.
---------------------------------

DCOPClient::attachInternal. Attach failed Could not open network socket
KCrash: Application 'kate' crashing...
Warning: connect() failed: : Connection refused
KCrash cannot reach kdeinit, launching directly.
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
drkonqi: cannot connect to X server :0.0

... then kate crashes, but most of the time i will receive this:

$ sudo kate myfile.txt
DCOPClient::attachInternal. Attach failed Could not open network socket
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-6200' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.

... then kate opens and everything works as expected, no more errors untill i reboot again

This problem is exactly the same as i experienced in Kubuntu Edgy except i minor detail 'Xlib: Invalid MIT-MAGIC-COOKIE-1 key' what the heck is this? Ive only been receiving 'Xlib: Invalid MIT-MAGIC-COOKIE-1 key' for a couple of weeks now.

TyphoonX