Bug 380788 - Could not start process Cannot talk to klauncher:
Summary: Could not start process Cannot talk to klauncher:
Status: RESOLVED FIXED
Alias: None
Product: rkward
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR normal
Target Milestone: ---
Assignee: RKWard Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 00:43 UTC by RKWard Team
Modified: 2011-09-18 10:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RKWard Team 2011-07-05 00:43:14 UTC
-- Originally posted by (AT sourceforge.net): cratyle --

-- This ticket was imported from http://sourceforge.net/p/rkward/bugs/93 on 2017-05-30 15:27:01 +0100 --
Here's the complete message when I try to open or save a script R file.

"Could not start process Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files."

There is a workaround :

Start a new script file within Rkward
Copy and paste your script file in Rkward
Work with this file within Rkward
Copy and paste back to your original script file if you made any changes

I use :

Rkward 0.5.6
KDE 4.5.4
R 13.0
-- Labels: user interface --
Comment 1 RKWard Team 2011-07-05 01:10:17 UTC
-- Originally posted by (AT sourceforge.net): cratyle --
I encounter the same bug when I try to copy a line from the console to the output. Here's the full message. Below, at Additionnal information, the same message reappear.

The requested operation could not be completed
Cannot Initiate the file Protocol
Technical Reason: Unable to Launch Process
Details of the Request:
URL: file:///C:/Documents and Settings/Francois/.rkward/rk\_out.html
Protocol: file
Date and Time: July 4, 2011 10:03 pm

Additional Information: Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files

Description:
The program on your computer which provides access to the file protocol could not be started. This is usually due to technical reasons.
Possible Causes:
The program which provides compatibility with this protocol may not have been updated with your last update of KDE. This can cause the program to be incompatible with the current version and thus not start.
You may have encountered a bug in the program.
Possible Solutions:
Update your software to the latest version. Your distribution should provide tools to update your software.
Contact your appropriate computer support system, whether the system administrator, or technical support group for further assistance.

I use :

Rkward 0.5.6
KDE 4.5.4
R 13.0
Comment 2 Thomas Friedrichsmeier 2011-07-05 06:46:09 UTC
Hi\!

Thanks for reporting.

One frequent cause for "Cannot talk to klauncher" errors is that some KDE services are already running on a different user account, or - esp. if installation did not work on the first attempt - from a different version of KDE. The best way to rule out this cause is to reboot your system. Does the problem persist after a reboot?

If the problem persists, could you check your virus scanner and firewall logs for any indication that klauncher or dbus-daemon have been blocked?

Regards
Thomas
Comment 3 RKWard Team 2011-07-05 12:32:59 UTC
-- Originally posted by (AT sourceforge.net): cratyle --
Rebooting do the job. The problems seems to be an old version of KDE on my computer.

Merci.
Comment 4 Thomas Friedrichsmeier 2011-09-18 10:28:22 UTC
Thanks for your feedback.

I have finally added a note about this problem to https://sourceforge.net/apps/mediawiki/rkward/index.php?title=RKWard\_on\_Windows .

Closing this report.
Comment 5 Thomas Friedrichsmeier 2011-09-18 10:28:22 UTC
- **assigned_to**: nobody --> tfry
- **status**: open --> closed