Home > Klauncher Could > Klauncher Could Not Be Reached Via Dbus

Klauncher Could Not Be Reached Via Dbus

Then click on enable. Comment 18 Ivo Anjo 2008-07-07 19:23:11 UTC Thanks for fixing it, this is one of those bugs that is really annoying. The error when launching kcachegrind was 169017, fixed. Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. check over here

Reply With Quote 04-Mar-2010,09:16 #4 hcvv View Profile View Forum Posts View Blog Entries View Articles Global Moderator Join Date Jun 2008 Location Netherlands Posts 20,187 Re: D-bus error You did Could it be that there is a racing condition between the two ? Check if you have started the DBUS server. kdeinit4: Communication error with launcher. http://www.linuxquestions.org/questions/linux-general-1/klauncher-could-not-be-reached-via-d-bus-what-do-i-do-650287/

When I launch a new konqueror process, the message "Konqueror didn't close correctly" appears, even though the previous session is still running, and the new process works fine, like every other After download, I clicke the RPM which then launches last..... Board index New Topic Find a Solution KDE Links Top Top The team • Delete all board cookies Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group © Copyright 2012

Check if you have started the DBUS server. What happens when you start YaST from the Kmenu? Do you get the error during that download? Check if you have started the DBUS server.

Do you want me to include here the output from the kde4-config stuff? When I get a chance I'll log out and back in and let you know what happened. While clicking on an icon (panel, desktop...) pops up a window with : KLauncher could not be reached via D-Bus, error when calling start_service_by_desktop_name: empty After this incident, there is only check these guys out klauncher failing...

I don't know enough yet to understand the message. You will have to register before you can post in the forums. (Be aware the forums do not accept user names with a dash "-") Also, logging in lets you avoid You are currently viewing LQ as a guest. So it seems that something (klauncher?) is having trouble starting kate in this case, it's not a problem with kate.

etc. https://forums.gentoo.org/viewtopic-t-942668-start-0.html I just installed Kubuntu 8.10 running KDE 4.1.3. So, 1) klauncher has to give a better error message in this case (I can have a look at that) 2) the kate .desktop file is wrong. k3b(13451)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory!

I changed %U into %u %U is correct; kate can handle multiple urls in the command line. check my blog Comment 40 David Faure 2008-12-16 02:30:47 UTC The error message with "empty" is fixed for 4.2 (possibly even 4.1.3, I forgot if I backported that one). If it is Linux Related and doesn't seem to fit in any other forum then this is the place. The same QFileDialog::getSaveFileName() works when used from a different application so the question would be why doesnt' the same call work from VirtualBox ?

Tom Taylor - retired penguin AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata3 openSUSE 12.3x86_64 openSUSE 13.1-M2x86_64 KDE 4.8.5, FF 14.0.1 - 8- KDE 4.10.0, FF 20.0 registered Can you check the set up? Comment 20 Ivo Anjo 2008-07-08 16:21:47 UTC It seems this also happens with ktorrent that has X-DBUS-StartupType=Single . http://jessriegel.com/klauncher-could/klauncher-could-not-be-reached-by.html Join our community today!

Can you try to find out if this line makes the difference, or which other line makes a difference? KLauncher could not be reached via D-Bus. klauncher(999) kdemain: No DBUS session-bus found.

k3b(13451): couldn't create slave: "Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files" k3b(13451): couldn't create slave: "Cannot talk to klauncher: The name org.kde.klauncher was not

klauncher: Exiting on signal 15 klauncher(980) kdemain: No DBUS session-bus found. Comment 26 Pino Toscano 2008-07-18 10:10:35 UTC *** Bug 166895 has been marked as a duplicate of this bug. *** Comment 27 auxsvr 2008-07-19 20:35:40 UTC Created attachment 26268 [details] dbus-monitor Topics: Active | Unanswered Index »Applications & Desktop Environments »[SOLVED] k3b acting up Pages: 1 #1 2014-11-01 15:33:15 inflextau Member Registered: 2014-06-28 Posts: 13 [SOLVED] k3b acting up HiI've a system There is also a KDE bug for it: http://bugs.kde.org/show_bug.cgi?id=157407 Björn Streicher (bstreicher) on 2008-03-30 Changed in meta-kde4: status: New → Confirmed Eduardo Besembel (besembel) wrote on 2008-05-13: #3 instantánea1.jpeg Edit (48.6

You should not do that since it most likely will not work kdeinit4: Shutting down running client. Is KDEDIRS set to kde4? If you'd like to contribute content, let us know. http://jessriegel.com/klauncher-could/klauncher-could-not-reached.html But removing also the X-DBUS-StartupType line seems to have fixed it ...

In the Application tab, change the %U to %u in the command field, and it should work . If you need to reset your password, click here. every time I log into my kubuntu system I get this error. "KLauncher could not be reached via D-Bus, error when calling start_service_by_desktop_path:empty" I click the ok button and everything seems Exiting!

Here is the link for you to look over if you need to. Thanks. The system froze for a few moments and then I got the following error: KLauncher could not be reached via D-Bus. Check if you have started the DBUS server.

Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ just fixed the ktorrent side of the issue... Are you new to LinuxQuestions.org? Report a bug This report contains Public information Edit Everyone can see this information.

kdeinit4: Communication error with launcher. Check if you have started the DBUS server. Edit bug mail Other bug subscribers Subscribe someone else Bug attachments pilt3.png (edit) instantánea1.jpeg (edit) Add attachment Remote bug watches kde-bugs #157407 [RESOLVED DUPLICATE] Edit novell-bugs #361509 [RESOLVED DUPLICATE] Edit Bug Check if you have started the DBUS server.

Check if you have started the DBUS server. klauncher(1005) kdemain: No DBUS session-bus found. Subscribing... dc Comment 1 Richard Johnson 2008-02-23 07:40:23 UTC Hey David, I have run across quite a few of these now on Launchpad, however one guy attached some fairly decent traces as

At home I get the same error and when I click ok Kde4 shuts down and restarts.