Version: (using KDE 4.3.1) OS: Linux Installed from: Debian testing/unstable Packages When many KDE applications(e.g Konsole, or System-settings, or KMail, but not Kwrite, and maybe more exceptions) are started, a Message appears stating "Error launching /usr/share/applications/kde4/KMail.desktop. Either KLauncher is not running anymore, or it failed to start the application." However, the application window still appears (except for Kmail, but that appears to be a different bug). .xsession-errors also reports a number of DBUS-related NoReply errors. This file is at http://pastebin.ca/1562986
I get this error as well, yet the application does launch as per original post. " Error launching /usr/share/applications/kde4/kwrite.desktop. Either KLauncher is not running anymore, or it failed to start the application. "
(In reply to comment #1) > I get this error as well, yet the application does launch as per original post. > > " > Error launching /usr/share/applications/kde4/kwrite.desktop. Either KLauncher > is not running anymore, or it failed to start the application. > " Sorry to not specify, I am running KDE 4.3.1 on Debian Sid, and unlike the original post, this does happen for KWrite as well.
Running this on my Debian system seems to have fixed the error: shell$ sudo aptitude reinstall dbus dbus-x11
> Running this on my Debian system seems to have fixed the error: > shell$ sudo aptitude reinstall dbus dbus-x11 I take that back; it seemed to have fixed it earlier today but the error has returned; this happens always, with both local files and with sftp:/ accessed files (KIO-slave access) This is still an issue for me.
This does not seem to happen with a new user account on my system, pointing to something within my own settings somewhere as the culprit.
Deleting my ~/.dbus/ folder seems to have done the trick thus far; I'll report back if the issue crops up again but everything is much more responsive now.
The issues has returned; again removing the .dbus/ folder has fixed it but I am not sure what is causing it. Here are the contents of my .dbus/ files if it helps at all. A new .dbus/ folder has not yet been created: jthomas@jthomas:11:47:~$ cat .dbus-broken/session-bus/95e1f5e98db58a81cecd759048727625-0 # This file allows processes on the machine with id 95e1f5e98db58a81cecd759048727625 using # display :0 to find the D-Bus session bus with the below address. # If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will # be used rather than this file. # See "man dbus-launch" for more details. DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-5cNahm0C7E,guid=b8ec7a9ed60e5b31c8a43cac4addbe37 DBUS_SESSION_BUS_PID=25931 DBUS_SESSION_BUS_WINDOWID=4194305 jthomas@jthomas:11:47:~$ cat .dbus-broken/session-bus/95e1f5e98db58a81cecd759048727625-1 # This file allows processes on the machine with id 95e1f5e98db58a81cecd759048727625 using # display :1 to find the D-Bus session bus with the below address. # If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will # be used rather than this file. # See "man dbus-launch" for more details. DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-NBI40YORhE,guid=66384ad62f4a7662fa36455a4ad5d9b6 DBUS_SESSION_BUS_PID=31125 DBUS_SESSION_BUS_WINDOWID=4194305 Any chance this is a KDESudo issue? I have a script that runs that at login every day; however its been a week of functioning before returned, so I am not certain that is the issue. Just a thought.
The .dbus/ folder and contents seems to get recreated at login; here is my current folder contents which differs from what I posted before; what would cause these differences? jthomas@jthomas:15:01:~$ cat .dbus/session-bus/95e1f5e98db58a81cecd759048727625-0 # This file allows processes on the machine with id 95e1f5e98db58a81cecd759048727625 using # display :0 to find the D-Bus session bus with the below address. # If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will # be used rather than this file. # See "man dbus-launch" for more details. DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-gxeEmslhTB,guid=c2512faca8ac76a097ccac264ade1634 DBUS_SESSION_BUS_PID=3865 DBUS_SESSION_BUS_WINDOWID=4194305 To alleviate my own issues (but not as a bug fix) I created a script in ~/.kde/shutdown/ folder (create it if it doesn't exist) called 'rm_dbus.sh' and made it executable; it contains the following lines if someone else needs to do this. At each logout of KDE, this script will run: #!/bin/bash /bin/rm -rf ~/.dbus/
I also get the same problem. It first occurred after my recent update to KDE 4.3.4 from 4.3.3. I'm using Arch Linux. This problem also exists with non-KDE programs. For example open office: "Error launching /usr/share/applications/draw.desktop. Either KLauncher is not running anymore, or it failed to start the application." The startup takes a very long time (ca 30sec), after ca 20sec the error is shown and then after another 10sec the program starts up. Deleting the dbus directory or even restarting dbus didn't help.
(In reply to comment #9) > I also get the same problem. It first occurred after my recent update to KDE > 4.3.4 from 4.3.3. I'm using Arch Linux. same problem here: slackware64-current, kde 4.3.4 > This problem also exists with non-KDE programs. For example open office: > "Error launching /usr/share/applications/draw.desktop. Either KLauncher is not > running anymore, or it failed to start the application." indeed also firefox & thunderbird > The startup takes a very long time (ca 30sec), after ca 20sec the error is > shown and then after another 10sec the program starts up. X also eat 20% cpu time, on a core2 e4500 The only work-around for me is to restart X. Any feedback are welcome.
(In reply to comment #9) > I also get the same problem. It first occurred after my recent update to KDE > 4.3.4 from 4.3.3. I'm using Arch Linux. > > This problem also exists with non-KDE programs. For example open office: > "Error launching /usr/share/applications/draw.desktop. Either KLauncher is not > running anymore, or it failed to start the application." > > The startup takes a very long time (ca 30sec), after ca 20sec the error is > shown and then after another 10sec the program starts up. > > Deleting the dbus directory or even restarting dbus didn't help. upgrade to dbus 1.2.6 (from 1.2.4): I'm not able to reproduce the problem anymore. Anyone can confirm?
I think I've worked out what causes this bug. When the application is launched, klauncher waits 30 seconds for a dbus acknowledgement that the application has started. If this is not recieved, it assumes the program has failed to launch and displays the error message. When the computer is so slow it takes more than 30 seconds to send the acknowledgement, the program starts, but the error is still displayed
I am running Debian Sid on a rather fast computer, and this does not happen on a slower computer at my house (which was built with a much more fresh installation than this one with the issue), so I do not think that is the problem. I have this dbus currently installed: $ aptitude show dbus Package: dbus State: installed Automatically installed: yes Version: 1.2.16-2 I cannot confirm if this newer version is not having those issues or not, since I have implemented the script in Comment #8 everything is working for me but obviously its not the ideal solution. I've not yet tried without that script since initially implementing it. https://bugs.kde.org/show_bug.cgi?id=207184#c8
It happened again today :-((
I get this with KDE 4.4.0. "Sorry - Plasma Workspace" "Error launching /usr/share/applications/kde4/kwrite.desktop. Either KLauncher is not running anymore, or it failed to start the application." I did _not_ notice this with other applications, than Kwrite. It seems, that (at least in my system) it has something to do with timeouts. I get this message from time to time, when I open text file from 'Folder View' widget. In that case Kwrite starts slowly and only after the message. If I close Kwrite and open it a moment later again, it starts promptly (I think that is because of some kind of disk cash) and no message is displayed. While I typed the information above, I closed Kwrite, and tried to open it again. I get the same pop up message and again Kwrite starts only after it (whole procedure is loooong - 10-20 seconds). I tried it once more after a couple of minutes - message is displayed again. And, what is interesting, clock in my plasma panel freezes (normally I can see seconds elapse, but before message the number just stays the same). So it is 100% reproducible.
Confirmed. This only happens sometimes. Dbus 4.8 Gentoo. KDE 4.14.3.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!