Bug 191388

Summary: Can't launch programs from context-menu as root
Product: [openSUSE] openSUSE 10.2 Reporter: Andreas Schlehahn <linuxdreas>
Component: KDEAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: suse-beta, wstephenson
Version: Final   
Target Milestone: ---   
Hardware: x86   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Andreas Schlehahn 2006-07-10 20:44:36 UTC 
When I start Konqueror in Super User Mode I sometimes can not start any application from the context menu, e.g. right-click on fstab: An error message "KDEInit could not launch 'kate'." pops up. This behaviour only happens once in a while, I could not find any pattern yet.
Comment 1 Will Stephenson 2007-08-12 07:09:37 UTC 
Can't reproduce this on 10.2 or 10.3.  Have you seen it since then, on newer versions than 10.1?
Comment 2 Will Stephenson 2007-08-12 07:09:53 UTC 
Can't reproduce this on 10.2 or 10.3.  Have you seen it since then, on newer versions than 10.1?
Comment 3 Andreas Schlehahn 2007-08-14 04:06:05 UTC 
(In reply to comment #2 from Will Stephenson)
> Can't reproduce this on 10.2 or 10.3.  Have you seen it since then, on newer
> versions than 10.1?
> 

I still see it with openSUSE 10.2 (all updates except last kernel update).  It is quite reliably reproduceable by doing this:
Start Konqueror (Super user Mode)
Open a textfile (e.g. /etc/fstab) in kwrite
Close the Konqueror window

Now, the next time I start Konqueror in SuperUser Mode,  I get the error message when I try to open any file via the context menu. 

It helps to kill the process 'dcopserver' for root. I also tried to terminate the processes kded and kdeinit, but that usually leads to another error message about 'klauncher'.

HTH
Andreas
Comment 4 Stephan Kulow 2007-10-01 15:18:52 UTC 
The info is provided
Comment 5 Lubos Lunak 2008-07-30 15:15:44 UTC 

*** This bug has been marked as a duplicate of bug 411537 ***