Bug 157407 - KLauncher could not be reached via D-Bus
Summary: KLauncher could not be reached via D-Bus
Status: RESOLVED DUPLICATE of bug 157853
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-08 10:36 UTC by dc
Modified: 2008-07-13 02:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dc 2008-02-08 10:36:05 UTC
Version:           Palsma on KDE 4.0.1 (using KDE 4.0.0)
Installed from:    Ubuntu Packages
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22-14-generic

Got the following message after trying to select another Desktop in the pannel :

KLauncher could not be reached via D-Bus, error when calling start_service_by_desktop_path: empty

Does seem to occur also when trying to launch any application from pannel, desktop, etc. 

This "notifier-message" will never occur again, once we click the "close" button. Meaning, ot occurs only once after KDE startup when trying to launch an application; or anything wich requires the klauncher. Also, a ps shows two klauncher processes.

dc        6068  6067  0 10:06 ?        00:00:00 klauncher
dc        6158  6142  0 10:07 ?        00:00:00 klauncher [kdeinit]

Is the first one trying to race the other ?
Comment 1 dc 2008-02-08 10:37:30 UTC
Kde version used is : 4.0.1
Comment 2 Björn Streicher 2008-03-30 15:23:40 UTC
I'm having the same problem. There are also reports in the Ubuntu launchpad (https://bugs.launchpad.net/ubuntu/+source/meta-kde4/+bug/204728) and for Opensuse 10.3: https://bugzilla.novell.com/show_bug.cgi?id=361509
Comment 3 Yuri Pikin 2008-05-11 13:38:16 UTC
I`m having the same problem. Using KDE 4.0.3
Comment 4 Xavier Brochard 2008-06-07 18:39:28 UTC
Same problem here, using kate or kword, with latest Debian packages (KDE 4.1 beta). After a second launch, the message is something like "KDEinit can't launch /usr/bin/kate" (or /usr/bin/kword). No problem with Kwrite. 
%u should be change to %U in files association.

Comment 5 Cyrill Helg 2008-07-01 16:31:05 UTC
I'm having the same problem with a current svn build. This happens to when I launch a kde4 app e.g. kile.
Comment 6 A. Spehr 2008-07-13 02:49:55 UTC
From comments on bug #155905, I take it this is fixed in 4.0.5 & 4.1

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