Kdevelop will not launch after successful installation

[namu.patel7@…]

Hi all,

I just installed Kdevelop and followed the directions on the KDE:wiki.

Kdevelop was installed to /opt/local/bin:

namu.patel$ ls /opt/local/bin/kdev*

/opt/local/bin/kdevelop!
/opt/local/bin/kdevplatform_shell_environment.sh

When I try to launch Kdevelop, I recieve the message:

namu.patel$ kdevelop\! &
[1] 36259
namu:~ namu.patel$ /opt/local/bin/kdevelop!: line 31: /opt/local/bin/kdevelop: No such file or directory
Error: Failed retrieving a pid.

Can someone please help. Thank you.

[larryv (Lawrence Velázquez)]

Thanks. In the future, please Cc relevant port maintainers and use WikiFormatting.

[NicosPavlov]

The KDE applications do not install in /opt/local/bin, but as bundles in /Applications/MacPorts/KDE4. Just double-clicking the bundle should launch it.

[namu.patel7@…]

Replying to nicos@…:

The KDE applications do not install in /opt/local/bin, but as bundles in /Applications/MacPorts/KDE4. Just double-clicking the bundle should launch it.

I tried opening KDevelop from ~/Appliations/MacPorts/KDE4/kdevelop by clicking on the icon but it still opens for a second and crashes right away before it is even loaded up. I can't sem to locate the crash log either.

[namu.patel7@…]

If I run the executable found inside ~/Appliations/MacPorts/KDE4/kdevelop, I see a crash report.

namu:~ namu.patel$ /Applications/MacPorts/KDE4/kdevelop.app/Contents/MacOS/kdevelop ; exit;
QIODevice::setTextModeEnabled: The device is not open
kdevelop(37892)/KSharedDataCache ensureFileAllocated: This system misses support for posix_fallocate() -- ensure this partition has room for at least 10547296 bytes. 
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
kdevelop(37892)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
KCrash: Application 'kdevelop' crashing...
KCrash: Attempting to start  from kdeinit
sock_file=/Users/namu.patel/Library/Preferences/KDE/socket-namu/kdeinit4__tmp_launch-SpP7ty_org.x_0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start  directly
KCrash failed to exec(), errno = 2
logout

[Process completed]

If I enter the command export $(dbus-launch), I get the below message.

namu:~ namu.patel$ export $(dbus-launch)
Failed to start message bus: launchd's environment variable DBUS_LAUNCHD_SESSION_BUS_SOCKET is empty, but should contain a socket path.

EOF in dbus-launch reading address from bus daemon
declare -x Apple_PubSub_Socket_Render="/tmp/launch-ScyCdg/Render"
declare -x COMMAND_MODE="unix2003"
declare -x DISPLAY="/tmp/launch-SpP7ty/org.x:0"
declare -x HOME="/Users/namu.patel"
declare -x LANG="en_US.UTF-8"
declare -x LOGNAME="namu.patel"
declare -x OLDPWD
declare -x PATH="/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/texbin:/usr/X11/bin"
declare -x PWD="/Users/namu.patel"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_AUTH_SOCK="/tmp/launch-4yAXTR/Listeners"
declare -x TERM="xterm-color"
declare -x TERM_PROGRAM="Apple_Terminal"
declare -x TERM_PROGRAM_VERSION="273.1"
declare -x TMPDIR="/var/folders/-B/-Bx-9dMNE1SY4WCBuwUEzk+++TM/-Tmp-/"
declare -x USER="namu.patel"
declare -x __CF_USER_TEXT_ENCODING="0x1F6:0:0"

I really do not know how get KDevelop to work. Does anyone have any suggestions?

Thank you, namu

[hlprasu@…]

I am also facing the same issue. Hope to see this resolved soon. Please let me know if any information needs to be provided.

[hlprasu@…]

Just figured out that I didn't run commands as given in wiki:KDE#Stepsrequiredafterinstallation

After that, kdevelop has started to run. I'm yet to fully check its functionality. But at least, a proper UI is showing up now.

Hope this helps.

Replying to hlprasu@…:

I am also facing the same issue. Hope to see this resolved soon. Please let me know if any information needs to be provided.

[NicosPavlov]

Replying to namu.patel7@…:

If I run the executable found inside ~/Appliations/MacPorts/KDE4/kdevelop, I see a crash report.

[snip]
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
kdevelop(37892)/kdeui (kdelibs): Session bus not found 

As you suspect, the dbus daemon is not launched, making kdevelop crash. You can find the required commands by typing

port notes dbus

or follow the instructions at Installing KDE applications.

I close the ticket as it does not appear to be a bug. Support is typically provided on the mailing list.

[NicosPavlov]

Apparently, the issue is present even after having loaded the dbus daemon.

In that case, the problem seems to be at dbus level, but just to be sure, are simpler KDE applications such as konqueror (provided by kde4-baseapps) also crashing ?

[namu.patel7@…]

Replying to nicos@…:

Apparently, the issue is present even after having loaded the dbus daemon.

In that case, the problem seems to be at dbus level, but just to be sure, are simpler KDE applications such as konqueror (provided by kde4-baseapps) also crashing ?

Konqueror also is crashing. I just went through a clean install of MacPorts and KDevelop. I even deactivated and reactivated the dbus, but the problem persists.

Below is the crash report I get when running Konqueror.

Last login: Wed May 22 16:23:12 on ttys003
namu:~ namu.patel$ /Applications/MacPorts/KDE4/konqueror.app/Contents/MacOS/konqueror ; exit;
QIODevice::setTextModeEnabled: The device is not open
konqueror(12249)/KSharedDataCache ensureFileAllocated: This system misses support for posix_fallocate() -- ensure this partition has room for at least 10547296 bytes. 
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
konqueror(12249)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
KCrash: Application 'konqueror' crashing...
KCrash: Attempting to start /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi from kdeinit
sock_file=/Users/namu.patel/Library/Preferences/KDE/socket-namu/kdeinit4__tmp_launch-gTCNXd_org.x_0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /opt/local/lib/kde4/libexec/drkonqi.app/Contents/MacOS/drkonqi directly
QIODevice::setTextModeEnabled: The device is not open
QProcess: Destroyed while process is still running.
drkonqi(12253)/KSharedDataCache ensureFileAllocated: This system misses support for posix_fallocate() -- ensure this partition has room for at least 10547296 bytes. 
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
drkonqi(12253)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
logout

[Process completed]

I am running 64 bit OS X 10.6.8 MacPorts 2.1.3-10 XCode 3.2.6

As for KDE4, I currently have installed

kde4-baseapps                  @4.10.3         kde/kde4-baseapps
kde4-filelight                 @4.10.3         kde/kde4-filelight
kde4-kile                      @2.1.3          tex/kde4-kile
kde4-runtime                   @4.10.3         kde/kde4-runtime

[NicosPavlov]

It seems clear that dbus is the issue, but as the daemons seem to be loaded, it is harder to get why it crashes. If the daemons are working correctly (which is not sure), there should be two processes "dbus-daemon", as you can check with for instance the Activity Monitor. If not, the daemons are not working as expected, as the error you showed in one of your reports seem to indicate. In this case, it could be possible to try to manually start the dbus processes with the commands

sudo /opt/local/bin/dbus-daemon --system --nofork
sudo /opt/local/bin/dbus-daemon --nofork --session

for respectively the system and user processes.

It should also be possible to check in the file system.log for potential errors at startup when the processes should be started by launchd.