This is the first error in my collection! I’m not sure why it inspired me. It is a pretty typical error message.
This specimen is of the pop-up error message variety, when you click something and get it instead of what you want. In this case I was trying to start a terminal program in the K Desktop Environment (KDE 2) on a Silicon Graphics machine. The title bar of the pop-up box says “Sorry – KDE Panel”. I like an apologetic message that doesn’t make you feel like it’s all your fault, even though you are probably screwed regardless.
The real test of an error message, though, is whether it gives you any clue how to repair the situation. I have no idea what DCOP is, but I checked all the running programs and found that there is indeed something called kdeinit: dcopserver running. So it’s running, but it cannot be used to reach ‘KLauncher’. I also found a program called klauncher, but running it did nothing. Here my instinct was to restart KDE entirely, but I had a kind of important job running and didn’t want to risk interrupting it, so I just used another terminal.
How many times we do just give up in the face of an error, and find another way to do it? Often. There just isn’t time to figure out what’s really going on. Sometime I look to Google for help, and usually find many others who share my plight and few answers. Or, if I continue to dig, I get more information than I can digest, and again wave the white flag.
Sometime I find a solution. Maybe this collection will give me an idea how often.
10 responses to “KLauncher could not be reached via DCOP”
I did get an opportunity to restart KDE, which did away with the problem.
enuff of this stupid shit. nobody cares about yer stupid database.
As a real hobo i take offense at your suggestion that there are hobos (hobi?) in cyberspace..
Any real hobo that reads my Error Collection posts is OK by me, offended or no.
Man, guy, PLEASE include the answer to the problem or point at helpful links.
I googled to your page but it didnt really help me.
This is frustrating. 🙁
to fix this error just run “kdeinit”
“to fix this error just run “kdeinit””
Nope, that didn’t work for me. Got the following error:
“———————————
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /root/.DCOPserver_MyHost__1
and start dcopserver again.
———————————
DCOPClient::attachInternal. Attach failed Could not open network socket
“
Cool… kdeinit works, but why does this happen? I’m running on a sun box, solaris x64, kde 3.4 through blastwave… I have other machines running solaris x64 and have never seen the problem…
Thanks a lot for the tip tho!, it indeed fixes it…
hi i am running on ultravnc through which one can remotely access a server ( titan for example ) … and kdeinit is not working for me …plz help
hooiiiiiiiiiiiiiiii.
not workingggggggggggggggggg