Bug 124088

Summary: Could not start process Can't talk to klauncher
Product: [Applications] konqueror Reporter: Thorsten Staerk <dev>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Thorsten Staerk 2006-03-22 18:18:20 UTC 
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

I often get the error message "Could not start process Can't talk to klauncher" from konqueror. Using another user solves this problem. I would like to dig deeper into that problem. Could you please change the error message so that one knows what one can look for or could you assist me within this bug report ?
Comment 1 Thiago Macieira 2006-03-27 11:46:08 UTC 
Either klauncher isn't running or your DCOP session is busted.
Comment 2 Thorsten Staerk 2006-03-30 12:20:05 UTC 
The principal of bugzilla is that a user reports his problem how he sees it, and that we together then try to narrow down the root cause till we can fix it. So this bug is not invalid.

To narrow down the root cause: killall kdeinit makes the symptome go away.
Comment 3 Tommi Tervo 2006-03-30 12:37:56 UTC 
You kill some random KDE process (shoot blindly to your foot) and you expect program behave correctly after that?
Comment 4 Thiago Macieira 2006-03-31 18:29:27 UTC 
Ok, to help you: when you get that error message, the problem has already happened. You've got the symptom: cannot talk to klauncher.

Either klauncher died (for whichever reason) or the DCOP server did or the connection is somehow busted. There's not much that can be done for an error message.

If you want to dig deeper, check if klauncher is running or not and if your DCOP session is still working. You should be able to run "dcop klauncher" from the command-line and see some output.