Opened 9 years ago

Closed 9 years ago

#25178 closed defect (fixed)

klauncher does not work?

Reported by: tanim.islam@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: klauncher Cc: nerdling (Jeremy L), sharky@…, nicos_pavlov@…, cgilles (HumanDynamo), peter@…, m214089, l.laspada@…, wanthalf@…, bkn@…, michaelld (Michael Dickens), stevencbritton@…, terje.handeland@…, informatique@…, mkae (Marko Käning), astrofitz (Michael Fitzgerald), gamperl@…, juergen@…, hmeine (Hans Meine), MarcusCalhoun-Lopez (Marcus Calhoun-Lopez), develop@…, macports@…
Port:

Description

Whenever I try to run a KDE application, that involves opening a file dialog, or when I run khelpcenter to search through help info. I get the following error,

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

Anyone see anything like this? I get this error when opening the file dialog while running kile-devel.

I believe this is a high priority defect, because kde4 is unusable with this bug in place.

Change History (81)

comment:1 Changed 9 years ago by ryandesign (Ryan Schmidt)

Cc: snc@… sharky@… added

comment:2 Changed 9 years ago by nerdling (Jeremy L)

Priority: HighNormal

Seems there's an upstream bug that's been reopened and errors similar to this one are talked about in various places.

comment:3 Changed 9 years ago by mf2k (Frank Schima)

FYI, I just installed and launched kile-devel and was able to open a file with the open file dialog.

comment:4 Changed 9 years ago by nerdling (Jeremy L)

Cc: nicos_pavlov@… added

Tanim: Let's see what you've got installed:

port installed "kde*"

Any chance you've got an x86_64?

comment:5 in reply to:  4 Changed 9 years ago by tanim.islam@…

Replying to snc@…:

Tanim: Let's see what you've got installed:

port installed "kde*"

Any chance you've got an x86_64?

Yes, I have an x86_64 system. However, I did not change the default compilation options for macports. To the best of my knowledge, it should compile for x86, should it not?

comment:6 in reply to:  4 ; Changed 9 years ago by tanim.islam@…

Replying to snc@…:

Tanim: Let's see what you've got installed:

port installed "kde*"

Any chance you've got an x86_64?

I should mention the following error when I launch kile from the command line,

/Applications/MacPorts/KDE4/kile.app/Contents/MacOS/kile

kdeinit4: Aborting. bind() failed: Permission denied
Could not bind to socket '/Users/tanim/Library/Preferences/KDE/socket-odin000955814.ndc.nasa.gov/kdeinit4_'
kile(2619)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkonsolepart.so"
kile(2619) KIO::SlavePrivate::SlavePrivate: Connection server not listening, could not connect 
kdeinit4: Aborting. bind() failed: Permission denied
Could not bind to socket '/Users/tanim/Library/Preferences/KDE/socket-odin000955814.ndc.nasa.gov/kdeinit4_'
kile(2619): couldn't create slave: "Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files" 
kile(2619) KIO::SlavePrivate::SlavePrivate: Connection server not listening, could not connect 
kdeinit4: Aborting. bind() failed: Permission denied
Could not bind to socket '/Users/tanim/Library/Preferences/KDE/socket-odin000955814.ndc.nasa.gov/kdeinit4_'
kdeinit4: Aborting. bind() failed: Permission denied
Could not bind to socket '/Users/tanim/Library/Preferences/KDE/socket-odin000955814.ndc.nasa.gov/kdeinit4_'
kile(2619): couldn't create slave: "Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files" 

comment:7 in reply to:  6 Changed 9 years ago by nicos_pavlov@…

Replying to tanim.islam@…:

Replying to snc@…:

Tanim: Let's see what you've got installed:

port installed "kde*"

Any chance you've got an x86_64?

I should mention the following error when I launch kile from the command line,

/Applications/MacPorts/KDE4/kile.app/Contents/MacOS/kile

kdeinit4: Aborting. bind() failed: Permission denied Could not bind to socket '/Users/tanim/Library/Preferences/KDE/socket-odin000955814.ndc.nasa.gov/kdeinit4_'

It seems that the program does not have the proper rights to access files. Did you perform the step of changing the owner of the Preferences/KDE folder as required in the installation ?

######################################################
#  Programs will not start until you run the command 
#  'sudo chown -R $USER ~/Library/Preferences/KDE'  
#  replacing $USER with your username.              
######################################################

comment:8 Changed 9 years ago by peter@…

After updating kdebase4 yesterday I also get this error in e.g. kwrite. I have checked that the permissions are OK. When launching kwrite from the command line I see this:

wireless-176-183:~ peter$ /Applications/MacPorts/KDE4/kwrite.app/Contents/MacOS/kwrite &
[1] 32158
wireless-176-183:~ peter$ kwrite(32158)/kdeui (KIconLoader) KSharedDataCache::Private::mapSharedMemory: Failed to establish shared memory mapping, will fallback to private memory -- memory usage will increase 
kdeinit4: (klauncher /opt/local/lib/kde4/libexec/klauncher) Pipe closed unexpectedly
kdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (kded4 /Applications/MacPorts/KDE4/kded4.app/Contents/MacOS/kded4) Pipe closed unexpectedly
kdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: Communication error with launcher. Exiting!

comment:9 in reply to:  8 Changed 9 years ago by nerdling (Jeremy L)

Replying to peter@…:

And you did startup dbus?

comment:10 Changed 9 years ago by cgilles (HumanDynamo)

Cc: caulier.gilles@… added

Cc Me!

comment:11 Changed 9 years ago by cgilles (HumanDynamo)

Same problem here after to have upgrated KDE 4.5.3 to 4.5.4

I uninstalled macports, and reinstalled it from scratch. I installed kdebase4 and kdesdk4. kate start but report the same problem :

kate(2658)/kdecore (kdelibs) getBundle: getBundle(): returning  "/Applications/MacPorts/KDE4/kdeinit4.app/Contents/MacOS/kdeinit4"
kate(2658): Couldn't start knotify from knotify4.desktop:  "KLauncher could not be reached via D-Bus. Error when calling start_service_by_desktop_path:
The name org.kde.klauncher was not provided by any .service files
" 

kdeinit4: Shutting down running client.
kate(2658)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Failed to execute program /opt/local/bin/knotify4: Unknown error: 0" 
kdeinit4: (klauncher /opt/local/lib/kde4/libexec/klauncher) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (kded4 /Applications/MacPorts/KDE4/kded4.app/Contents/MacOS/kded4) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (klauncher /opt/local/lib/kde4/libexec/klauncher) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (kded4 /Applications/MacPorts/KDE4/kded4.app/Contents/MacOS/kded4) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: Communication error with launcher. Exiting!
kdeinit4: (klauncher /opt/local/lib/kde4/libexec/klauncher) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (klauncher /opt/local/lib/kde4/libexec/klauncher) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (klauncher /opt/local/lib/kde4/libexec/klauncher) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (kded4 /Applications/MacPorts/KDE4/kded4.app/Contents/MacOS/kded4) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: Communication error with launcher. Exiting!
kdeinit4: (kded4 /Applications/MacPorts/KDE4/kded4.app/Contents/MacOS/kded4) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: Communication error with launcher. Exiting!
kdeinit4: (kded4 /Applications/MacPorts/KDE4/kded4.app/Contents/MacOS/kded4) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: Communication error with launcher. Exiting!

Gilles Caulier

comment:12 Changed 9 years ago by cgilles (HumanDynamo)

It sound like a problem with DBUS. But which one exactly ? DBUS work fine here :

new-host-3:~ agnes$ ps -ax | grep dbus
   52 ??         0:00.02 /opt/local/bin/dbus-daemon --system --nofork
  120 ??         0:00.10 /opt/local/bin/dbus-daemon --nofork --session
67713 ttys002    0:00.00 grep dbus

Gilles Caulier

comment:13 in reply to:  12 ; Changed 9 years ago by peter@…

Replying to caulier.gilles@…:

It sound like a problem with DBUS. But which one exactly ? DBUS work fine here :

new-host-3:~ agnes$ ps -ax | grep dbus

52 ?? 0:00.02 /opt/local/bin/dbus-daemon --system --nofork

120 ?? 0:00.10 /opt/local/bin/dbus-daemon --nofork --session

67713 ttys002 0:00.00 grep dbus

Gilles Caulier

Same here:

wireless-176-183:~ peter$ ps -ax | grep dbus 
70744 ??         0:00.01 /opt/local/bin/dbus-daemon --system --nofork
70748 ??         0:00.14 /opt/local/bin/dbus-daemon --nofork --session
87235 ttys000    0:00.00 grep dbus

comment:14 Changed 9 years ago by peter@…

Cc: peter@… added

Cc Me!

comment:15 in reply to:  13 Changed 9 years ago by peter@…

Replying to peter@…:

Replying to caulier.gilles@…:

It sound like a problem with DBUS. But which one exactly ? DBUS work fine here :

new-host-3:~ agnes$ ps -ax | grep dbus

52 ?? 0:00.02 /opt/local/bin/dbus-daemon --system --nofork

120 ?? 0:00.10 /opt/local/bin/dbus-daemon --nofork --session

67713 ttys002 0:00.00 grep dbus

Gilles Caulier

Same here:

wireless-176-183:~ peter$ ps -ax | grep dbus 70744 ?? 0:00.01 /opt/local/bin/dbus-daemon --system --nofork 70748 ?? 0:00.14 /opt/local/bin/dbus-daemon --nofork --session 87235 ttys000 0:00.00 grep dbus

To clarify, dbus runs but I still have the klauncher problem.

comment:16 Changed 9 years ago by dick.lam.1@…

I also have the klauncher problem, but this is happening after a successful build of Amarok.

richard-lams-macbook-pro:~ richardlam$ ps -ax | grep dbus
  148 ??         0:00.02 /opt/local/bin/dbus-daemon --system --nofork
  212 ??         0:00.22 /opt/local/bin/dbus-daemon --nofork --session
61196 ttys000    0:00.00 grep dbus

DBUS is definitely loaded already too. After closing the error Amarok stays open but nothing works. Any ideas?

comment:17 in reply to:  description Changed 9 years ago by m214089

Replying to tanim.islam@…:

Whenever I try to run a KDE application, that involves opening a file dialog, or when I run khelpcenter to search through help info. I get the following error,

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

Anyone see anything like this? I get this error when opening the file dialog while running kile-devel.

I believe this is a high priority defect, because kde4 is unusable with this bug in place.

I have the same problem after updating for digikam 1.6. I have removed the full macports installation and reinstalled. And yes, dbus is running properly and the permissions for ~/Library/Preferences/KDE are correct.

comment:18 Changed 9 years ago by m214089

Cc: luis.kornblueh@… added

Cc Me!

comment:19 Changed 9 years ago by cgilles (HumanDynamo)

I would to annotate that with KDE 4.5.3 + Qt 4.7.0, all been fine...

Now with KDE 4.5.4 and Qt 4.7.1, the problem appears...

I notified that not all KDE4 binary file as klauncher or knotify are not installed into /opt/local/bin (my macports install path). It's normal ?

This binary file are of course installed in /Applications/Macports/KDE4/...

Perhaps same shared libs for KDE4 or used by KDE4 are not installed properly ? This can breal internal process based on KIoslave, which lets application start but of course unsuitable for some use case (for ex try to open a file in kate editor)

I don't have a backup of my old KDE 4.5.3/Qt 4.7.0 macports dir to check...

Gilles Caulier

comment:20 Changed 9 years ago by l.laspada@…

I just installed Amarok, anytime I try to launch it I get the error message below.

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

Amarok will stay running but doesn't work.

DBUS is launched and working and I ran the command 'sudo chown -R (username) ~/Library/Preferences/KDE'

43 ??         0:00.01 /opt/local/bin/dbus-daemon --system --nofork
317 ??         0:00.16 /opt/local/bin/dbus-daemon --nofork --session

Does anyone knows how to solve this problem?

comment:21 Changed 9 years ago by l.laspada@…

Cc: l.laspada@… added

Cc Me!

comment:22 Changed 9 years ago by cgilles (HumanDynamo)

As all KDE 4.5.4 applications are currently broken, i recommend to trun priority of this file to "major".

Gilles Caulier

comment:23 Changed 9 years ago by wanthalf@…

Cc: wanthalf@… added

Cc Me!

comment:24 Changed 9 years ago by bkn@…

Cc: bkn@… added

Cc Me!

comment:25 Changed 9 years ago by michaelld (Michael Dickens)

Cc: michaelld@… added

Cc Me!

comment:26 Changed 9 years ago by stevencbritton@…

Cc: stevencbritton@… added

Cc Me!

comment:27 Changed 9 years ago by stevencbritton@…

This problem occurs in kdenlive as well.

comment:28 Changed 9 years ago by stevencbritton@…

Perhaps those involved in this project could revert us all back to 4.5.3 where it was working, so we can at least accomplish what we're working on in the meantime? This is a MAJOR bug.

comment:29 Changed 9 years ago by cgilles (HumanDynamo)

I agree. As KDE developper, (digiKam project), i confirm that all KDE applications work fine with 4.5.3. With 4.5.4, all is broken. This is a MAJOR bug. I vote to revert to 4.5.3...

Gilles Caulier

comment:30 Changed 9 years ago by stevencbritton@…

Just downgraded to 4.5.3 using MacPorts, however kdenLive won't run at all now, so a straight downgrade may not be the solution.

comment:31 in reply to:  29 ; Changed 9 years ago by nerdling (Jeremy L)

Replying to caulier.gilles@…: Developers should know how to install older versions of Portfiles.

Replying to stevencbritton@…: Unfortunately things won't just downgrade and work there's no sense rolling back the version of the portfiles.

Likely we can continue to wait for the next release (4.6) as it's right around the corner. If you're interested, I'll update the existing ports to be beta of the 4.5 branch. Any interested in this course of action instead?

comment:32 Changed 9 years ago by nerdling (Jeremy L)

I meant beta for the new 4.6 branch.

comment:33 in reply to:  31 Changed 9 years ago by stevencbritton@…

Replying to snc@…:

Replying to caulier.gilles@…: Developers should know how to install older versions of Portfiles.

Replying to stevencbritton@…: Unfortunately things won't just downgrade and work there's no sense rolling back the version of the portfiles.

Likely we can continue to wait for the next release (4.6) as it's right around the corner. If you're interested, I'll update the existing ports to be beta of the [4.6] branch. Any interested in this course of action instead?

I can't see how it can do any harm. Certainly can't make my problem any worse.

comment:34 Changed 9 years ago by nerdling (Jeremy L)

of course 4.5.86 kdelibs4 won't build (/opt/local/share/xml/common/l10n.xml is missing). Any ideas where it comes from?

comment:35 Changed 9 years ago by cgilles (HumanDynamo)

To snc@… : I'm interrested about KDE 4.6-beta1...

Gilles Caulier

comment:36 Changed 9 years ago by m214089

I'm too interested in kde-4.6-beta1 ...

comment:37 Changed 9 years ago by l.laspada@…

Lets try the new 4.6 branch.

Thank you.

comment:38 Changed 9 years ago by terje.handeland@…

Cc: terje.handeland@… added

Cc Me!

comment:39 Changed 9 years ago by informatique@…

Cc: informatique@… added

Cc Me!

comment:40 Changed 9 years ago by mkae (Marko Käning)

Cc: mk@… added

Cc Me!

comment:41 in reply to:  35 Changed 9 years ago by peter@…

Replying to caulier.gilles@…:

To snc@… : I'm interrested about KDE 4.6-beta1...

Gilles Caulier

I saw that new port files have been submitted for digikam 1.7. Were you able to work around the klauncher issue?

comment:42 Changed 9 years ago by stevencbritton@…

I have been waiting (patiently) for quite a while now for someone to say something, either here, on the KDE website, or somewhere else, and nobody seems to either care, or know anything about this issue.

Let me assure you all that this is a very serious issue, very real, and very frustrating. I am completely unable to work on my project using my Mac as a result of a base dependency of a working program being broken!

If I cannot trust the environment in which a program runs, it not only does damage to the framework, but also, through no fault of the program developer, them as well.

I am extremely disappointed that KDE would release a broken package to the community, and really hope that someone, anyone, does something to fix it sooner, rather than later.

comment:43 Changed 9 years ago by cgilles (HumanDynamo)

Do you tried to contact someone in #kde-devel IRC chanel from irc.freenode.net server ?

Gilles Caulier

comment:44 in reply to:  43 Changed 9 years ago by stevencbritton@…

Replying to caulier.gilles@…:

Do you tried to contact someone in #kde-devel IRC chanel from irc.freenode.net server ?

Gilles Caulier

Yes. No response.

comment:45 in reply to:  34 Changed 9 years ago by nerdling (Jeremy L)

Replying to snc@…:

of course 4.5.86 kdelibs4 won't build (/opt/local/share/xml/common/l10n.xml is missing). Any ideas where it comes from?

Fixed that bug in r74672. 4.6 rc1 is building for me so far (4.5.90).

comment:46 Changed 9 years ago by astrofitz (Michael Fitzgerald)

Cc: astrofitz@… added

Cc Me!

comment:47 Changed 9 years ago by mkae (Marko Käning)

I'd actually vote for going a step back (to KDE 4.5.3 ?) to have a non-broken KDE version officially served by MacPorts.

comment:48 Changed 9 years ago by informatique@…

I agree. On one of my Macs, this problem doesn't prevent my KDE apps from working (except that the open and save dialogs need some workabout), but on the other they don't even launch. I wouldn't mind a working version, even if it's a step back and I have to recompile a pile of packages.

comment:49 Changed 9 years ago by cgilles (HumanDynamo)

I vote for this solution too. KDE 4.5.3 have work very well... KDE 4.5.4 is unsuitable as well. It's a big problem !

I investigated a little bit why klauncher won't start, and in background, messages on the console report that a file is missing. But i cannot found which one exactly. I stay tuned on...

Gilles Caulier

comment:50 Changed 9 years ago by gamperl@…

Cc: gamperl@… added

Cc Me!

comment:51 Changed 9 years ago by cgilles (HumanDynamo)

This problem is not yet fixed.

I insist. this problem is major. ALL KDE4 application are broken.

There are 2 solutions :

QUESTION : how to install an old rev of a port. For example i tried this command :

# sudo port install kdebase4 @4.5.3

... and kdebase4 version 4.5.4 have been installed. Why ? What the right syntax to use ?

Gilles Caulier

comment:52 Changed 9 years ago by nerdling (Jeremy L)

We pointed out how to use older versions of Portfiles in comment 33. I'm not done testing 4.5.5 yet but it'll be out soon.

I wonder if dbus has had any changes…

comment:53 Changed 9 years ago by nerdling (Jeremy L)

KDE 4.5.5 in r74942.

comment:54 Changed 9 years ago by mkae (Marko Käning)

snc, great to see you've managed to lift us up to 4.5.5! You forgot, however, to remove this message from the portfile:

######################################################
#  Programs will not start until you run the command 
#  'sudo chown -R $USER ~/Library/Preferences/KDE'  
#  replacing $USER with your username.              
######################################################

which isn't an issue anymore since you incorporated D. Faure's patch to kdelibs4.

In case you've have 2nd thoughts about it, since a user might have wrong permissions from installation attempts in the past, then you might consider changing the wording from "will not start" to "might not start due to erroneously wrong permissions" or something like that.

(Haven't yet done any testing concerning the actual issue of this ticket.)

comment:55 Changed 9 years ago by mkae (Marko Käning)

:-(

I still see messages like these:

kmymoney(61574): couldn't create slave: "Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files" 
kdeinit4: Shutting down running client.
kdeinit4: Shutting down running client.

and

kdeinit4: (kded4 /opt/clean-slate/Applications/KDE4/kded4.app/Contents/MacOS/kded4) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: Communication error with launcher. Exiting!

Since the KDE upgrade doesn't solve this, I figure it's rather dbus which has to do its homework...

comment:56 Changed 9 years ago by juergen@…

Cc: juergen@… added

Cc Me!

comment:57 Changed 9 years ago by hmeine (Hans Meine)

Cc: hans_meine@… added

Cc Me!

comment:58 in reply to:  55 Changed 9 years ago by hmeine (Hans Meine)

Replying to mk@…:

I still see messages like these: "Cannot talk to klauncher: ..."

same here, uninstalled kde+ all dependents, installed 4.5.5 after selfupdate (using qt4-mac @4.7.1_0+mysql+quartz), but klauncher still does not work (dbus double-checked, session+system bus running fine)

(interestingly, it was exactly kmymoney which I am doing all this for right now..)

comment:59 Changed 9 years ago by nerdling (Jeremy L)

Cc: mcalhoun@… added

comment:60 Changed 9 years ago by nerdling (Jeremy L)

Has anyone tried downgrading DBus instead of KDE?

comment:61 in reply to:  54 ; Changed 9 years ago by nerdling (Jeremy L)

Replying to mk@…:

which isn't an issue anymore since you incorporated D. Faure's patch to kdelibs4.

I actually removed that patch, since upstream has finally fixed it.

The patches I added were mostly namespace issues that have cropped into this version (and 4.6 release candidates).

comment:62 Changed 9 years ago by bkn@…

Has anyone been able to get KDE running since the 4.5.4 upgrade? If so, how?

I've tried installing kdelibs4 verions 4.5.90, 4.5.95 (a.k.a the 4.6 betas) as well as kdelibs4 versions 4.5.3, 4.5.4, 4.5.5 by changing the Portfile, and always get the errors mentioned above.

comment:63 Changed 9 years ago by cgilles (HumanDynamo)

Exactly the same issue here with digiKam using KDE 4.5.5.

Kate editor report always the same error about klauncher...

Gilles Caulier

comment:64 in reply to:  61 Changed 9 years ago by mkae (Marko Käning)

Replying to snc@…:

I actually removed that patch, since upstream has finally fixed it.

Yep, that's what David promised for the 4.6 version. Great! (Still the warning messages should be changed accordingly.)

comment:65 in reply to:  60 Changed 9 years ago by mkae (Marko Käning)

Replying to snc@…:

Has anyone tried downgrading DBus instead of KDE?

DOWNgrade? To what? No, I tried to UPgrade to 1.4.1... (#27760)

comment:66 Changed 9 years ago by cgilles (HumanDynamo)

On this archive :

http://lists.kde.org/?l=kde-windows&m=116540483431670

I can see that some people have see this problem under windows with KDE4. As it's said, hacking command to try will be :

dbus-launch start klauncher start kded qdbus

I'm not running on my macbook currently. Somebody can test it ?

Gilles Caulier

comment:67 Changed 9 years ago by cgilles (HumanDynamo)

This is what's i can see on my macbook :

pctv:~ agnes$ uname -a
Darwin pctv.home 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386 i386
pctv:~ agnes$ qdbus
:1.4
org.freedesktop.DBus
pctv:~ agnes$

This confirm that failure is about klauncher which is not running. I think it's not a dbus fault.

The questions now :

  1. why klauncher is not started automatically when i start a KDE Application ?
  2. If i want to start it myself before to run a KDE application, how i can do it ?

Gilles Caulier

comment:68 Changed 9 years ago by cgilles (HumanDynamo)

AHHH...

I search about klauncher bin file on my macport installation.

There is no file like this in /opt/local/bin /opt/local/libexec /opt/local/sbin /Applications/MacPorts/KDE4.

Question : where i must find this bin file ? Why it's not installed on my system ?

Gilles Caulier

comment:69 Changed 9 years ago by cgilles (HumanDynamo)

There is an error in my previous post. Klauncher is in /opt/local/libexec:

bash-3.2$ pwd
/opt/local/lib/kde4/libexec
bash-3.2$ ./klauncher
klauncher: This program is not supposed to be started manually.
klauncher: It is started automatically by kdeinit4.
bash-3.2$ 

Now the question is why kdeinit4 cannont start klauncher :

bash-3.2$ pwd
/Applications/MacPorts/KDE4/kdeinit4.app/Contents/MacOS
bash-3.2$ ./kdeinit4
bash-3.2$ kdeinit4: (klauncher /opt/local/lib/kde4/libexec/klauncher) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (kded4 /Applications/MacPorts/KDE4/kded4.app/Contents/MacOS/kded4) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: Communication error with launcher. Exiting!

Which file is not found ?

Gilles Caulier

comment:70 Changed 9 years ago by develop@…

Cc: develop@… added

Cc Me!

comment:71 in reply to:  69 Changed 9 years ago by l.laspada@…

Replying to caulier.gilles@…:

There is an error in my previous post. Klauncher is in /opt/local/libexec:

I found it in /opt/local/lib/kde4/libexec/klauncher

sudo /opt/local/bin/kdeinit4_wrapper klauncher

gives:

kdeinit4_wrapper: Warning: connect(/Users/lorenzo/Library/Preferences/KDE/socket-mbp-i5.local/kdeinit4_) failed: : Connection refused
Error: Can not run klauncher !

comment:72 Changed 9 years ago by bkn@…

I did some testing (and my poor 4yr old laptop is tired of compiling). I was able to get Dolphin.app (w/ kdelibs 4.5.5 and 4.5.3) to display files w/o that annoying error we've all been seeing. The change that i made was i used the r72785 version of the workaround-kdeinit4-crash.patch. This patched was updated at the same time as the bump to KDE 4.5.4. I'm not all that familiar w/ this patch, but i believe this is a good place to start looking to fix this bug. I'll be looking at this patch, but if anyone else here know's this patch, perhaps you'll be able to find the problem quicker than i.

To Reproduce:

  • Download r72785 of from here
  • copy patch to /opt/local/var/macports/sources/rsync.macports.org/release/ports/kde/kdelibs4/files/
  • then compile kdelibs4 and cross your fingers.

comment:73 in reply to:  72 Changed 9 years ago by nerdling (Jeremy L)

The change in the patch was the removal of a removal. If you want to do this removal, it is now at line 559 in kinit/kinit.cpp.

comment:74 Changed 9 years ago by ryandesign (Ryan Schmidt)

I have gone back and fixed the formatting of many of the previous comments in this ticket. PLEASE remember to use the Preview button when writing a new comment, and if the formatting does not look correct, read WikiFormatting to learn how to format things correctly in this issue tracker. Specifically, use "{{{" and "}}}" around lines of code or commands.

comment:75 in reply to:  60 Changed 9 years ago by hmeine (Hans Meine)

Replying to snc@…:

Has anyone tried downgrading DBus instead of KDE?

According to the SVN revlog, the last update was from 1.2.16_1 to 1.2.24_1 8 months ago, right?

Just downgrading dbus (and restarting the daemons of course) led to:

Cannot find the D-Bus session server:  "Failed to connect to socket /tmp/launch-eqFevK/unix_domain_listener: Connection refused"

Unfortunately, recompiling kdelibs4 did not fix this - maybe one needs to rebuild qt4-mac, too (is QDbus used here)?

On the other hand, in the meantime bkn's hint looks much more promising than this.

comment:76 Changed 9 years ago by macports@…

Cc: macports@… added

Cc Me!

comment:77 in reply to:  72 ; Changed 9 years ago by peter@…

Replying to bkn@…:

To Reproduce:

  • Download r72785 of from here
  • copy patch to /opt/local/var/macports/sources/rsync.macports.org/release/ports/kde/kdelibs4/files/
  • then compile kdelibs4 and cross your fingers.

These steps worked for me. I can now run Dolphin, KWrite, and KMyMoney. Will test additional programs.

comment:78 in reply to:  77 Changed 9 years ago by paul@…

Replying to peter@…:

Replying to bkn@…:

To Reproduce:

  • Download r72785 of from here
  • copy patch to /opt/local/var/macports/sources/rsync.macports.org/release/ports/kde/kdelibs4/files/
  • then compile kdelibs4 and cross your fingers.

These steps worked for me. I can now run Dolphin, KWrite, and KMyMoney. Will test additional programs.

Digikam appears to work now as well!

comment:79 Changed 9 years ago by nerdling (Jeremy L)

Since it seems to be the culprit, I've put the removal in again in r75067.

Please let me know if revision 2 solves the issue without addition tinkering.

comment:80 in reply to:  79 Changed 9 years ago by peter@…

Replying to snc@…:

Since it seems to be the culprit, I've put the removal in again in r75067.

Please let me know if revision 2 solves the issue without addition tinkering.

Works for me.

comment:81 Changed 9 years ago by nerdling (Jeremy L)

Resolution: fixed
Status: newclosed

Alright then, it's fixed in r75067.

Note: See TracTickets for help on using tickets.