| Summary: | Mac OSX Build from binary factory does not start | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Ovidiu-Florin BOGDAN <kde.kfoar> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | grave | CC: | elvis.angelaccio, mail |
| Priority: | NOR | ||
| Version First Reported In: | 18.04.3 | ||
| Target Milestone: | --- | ||
| Platform: | macOS (DMG) | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Ovidiu-Florin BOGDAN
2018-08-16 12:32:43 UTC
Thanks for your bug report. One of my colleagues could confirm this problem as well. According to https://stackoverflow.com/questions/9066900/krusader-crashed-on-mac-osx-10-7-2, the same problem appeared with Krusader a few years ago. Could you try whether the solution presented (running launchctl load /Library/LaunchAgents/org.freedesktop.dbus-session.plist without sudo) does work? That'd be great. I've tried doing that, but I don't have that launch agent, even though I have dbus installed. We should write a guide for Mac users on how to install and setup dbus and put it in the KDE wiki under Mac. That seems like a good idea, but we'll need to be able to run dbus somehow first. Please try running 'echo $DBUS_LAUNCHD_SESSION_BUS_SOCKET' and '`brew --prefix qt`/bin/qdbus'. The first command should echo a valid path, e.g. /tmp/launch-EJDiyji/unix_domain_listener. The second command should show the available services, at least org.freedesktop.DBus. If this is not the case, then there's likely a problem with the installation of dbus. I'll dig a bit deeper and see what I can find. After I also installed Qt using brew, I got this: $ echo $DBUS_LAUNCHD_SESSION_BUS_SOCKET /private/tmp/com.apple.launchd.CB7Bp27AZj/unix_domain_listener $ `brew --prefix qt`/bin/qdbus :1.3 org.freedesktop.DBus |