"Cannot talk to klauncher"

09-05-2006	#1 (permalink)
Beowulf1976 Just Joined! Join Date: Sep 2006 Location: nr Stafford, UK Posts: 2	"Cannot talk to klauncher" I tried to enter Konqueror via sudo in Konsole so that I could place two files in a root folder, ie I typed: sudo konqueror I got the following error: Code: carol@carol-desktop:~$ sudo konqueror X Error: BadDevice, invalid or uninitialized input device 169 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 169 Major opcode: 147 Minor opcode: 3 Resource id: 0x0 Failed to open device ScimInputContextPlugin() konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher konqueror: ERROR: : couldn't create slave : Cannot talk to klauncher ~ScimInputContextPlugin() carol@carol-desktop:~$ Any ideas? I then tried kdesu konqueror instead after someone on the kubuntu forum said I shouldn't be using sudo to open GUI/Graphical stuff... but I got EXACTLY the same error. I'm so lost and really need some help on what I might have broken? changes prior to this error: 1. I have installed Automatix (the auto install from their website) and when it asked if I wanted the repositories (resource.list whatever) restored to the original I selected no. (oops?) 2. I have completely re-installed as I was dual booting with Ubuntu 6.06 so I DID have all the gnome stuff installed. (surely it's not, not working just because I no longer have gnome installed?) - bearing in mind that I have precious precious files on my Home directory, so I didn't touch that on the re-install - so there could still be gnomey stuff in there? rofl Things I have done so far: 1. Someone told me to type kdeinit in Konsole, I did and I got this: Code: carol@carol-desktop:~$ kdeinit kdeinit: Shutting down running client. --------------------------------- It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/carol/.DCOPserver_carol-desktop__0 and start dcopserver again. --------------------------------- KDE Daemon (kded) already running. kbuildsycoca running... Reusing existing ksycoca carol@carol-desktop:~$ - that was where I stopped, I didn't dare consider whether dcopserver (don't even know what it is) was still running and whether I should do what it said and remove that thingy. 2. I have been told the classic "switch it on and off again (rofl)"... to no avail. 3. Someone told me that it was my repositories that were causing the problem, but didn't actually suggest a solution so I found "the ultimate resource list" online and used Kate to edit my resource list - this didn't help at all, and now my resource.list is rather messy.. (let me know if you want to see this?) Now I'm sitting here, chewing on my desk (not literally of course, but this could change as I've been working on this problem ALL DAY now) wondering what on earth to do next. When giving replies/suggestions/fixes (hopefully the latter?! lol) Bear in mind that I'm a 30 year old frazzled mother of two psycho 6 week school holiday children who has been on codeine for 14 months, so my brain is rather fragile and I've only been using Linux for 2 - 3 months.

09-06-2006	#2 (permalink)
Beowulf1976 Just Joined! Join Date: Sep 2006 Location: nr Stafford, UK Posts: 2	Thanks to everyone for your speedy replies. I ended up having to do a complete re-install because no matter WHERE I asked for help no-one knew the solution

09-06-2006

#3 (permalink)

Dapper Dan

Super Moderator

Join Date: Oct 2004

Location: The Sovereign State of South Carolina

Posts: 4,136

Quote:

Originally Posted by Beowulf1976

Thanks to everyone for your speedy replies.

I ended up having to do a complete re-install because no matter WHERE I asked for help no-one knew the solution

I first saw your post AFTER you re-installed and could have given you some things to try...

Code:

sudo rm /your_home_directory/.DCOPserver_*__0

...and reboot.

The next time you have a problem, you might want to wait a tad longer than 16 hours for a reply before re-installing.

__________________
CRUX 2.5 + IceWM Registered:#371367 New Members: click here

Last edited by Dapper Dan; 09-06-2006 at 03:31 PM..

12-21-2006	#4 (permalink)
MadMan52 Just Joined! Join Date: Dec 2006 Posts: 1	I had the same problem and I just figured out what to do. You don't actually need to restart anything by the way. Just open a terminal and type this in as your user. dcopserver_shutdown kdeinit There problem fixed.

11-30-2007	#5 (permalink)
xaz0r Just Joined! Join Date: Jun 2006 Posts: 2	Thank you so much for this. This problem has been driving me crazy all day, but your fix worked like magic

Are you a Linux Guru who is willing to share your in-depth Linux knowledge? Try our new Article submission system.