Broken Krusader "krusader.shell"

[obmalcioglu@…]

Dear developers, I have recently built Krusader in a mid2010 macbook pro, osX 10.8, case sensitive filesystem. I can run the application by running /Applications/MacPorts/KDE4/krusader.app/Contents/MacOS/krusader however from the gui, the launch fails. When I try to run /Applications/MacPorts/KDE4/krusader.app/Contents/MacOS/krusader.shell I get

Applications/MacPorts/KDE4/krusader.app/Contents/MacOS/krusader.shell: line 4: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_krusader/krusader/work/build/krusader/krusader.app/Contents/MacOS/krusader: No such file or directory

Which is very true. The contents of the krusader.shell is this:

#!/bin/sh
# created by cmake, don't edit, changes will be lost

DYLD_LIBRARY_PATH=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_krusader/krusader/work/build/lib/./:/opt/local/lib${DYLD_LIBRARY_PATH:+:$DYLD_LIBRARY_PATH} "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_krusader/krusader/work/build/krusader/krusader.app/Contents/MacOS/krusader" "$@" 

best wishes, Baris

[mf2k (Frank Schima)]

In the future, please use WikiFormatting.

[mastak365@…]

Cc Me!

[mastak365@…]

I got same strange behaviour. I'm unable to run Krusader by clicking on the app, but it works in Terminal window with /Applications/MacPorts/KDE4/krusader.app/Contents/MacOS/krusader. Such the workaround was found by someone in ticket # 31655

BUT: 1) there are numerous error messages in Terminal window then:

KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work

krusader(2056)/KSharedDataCache ensureFileAllocated: This system misses support for posix_fallocate() -- ensure this partition has room for at least 10547296 bytes.

### the above line repeated many times ###

krusader(2056)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "The name org.kde.kded was not provided by any .service files" krusader(2056)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned kdeinit4: Shutting down running client. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) klauncher(2071) kdemain: Waiting for already running klauncher to exit. klauncher(2071) kdemain: Another instance of klauncher is already running! kdeinit4: Communication error with launcher. Exiting! /Applications/Krusader.command: line 1: 2056 Terminated: 15 /Applications/MacPorts/KDE4/krusader.app/Contents/MacOS/krusader

2) Krusader actually can't run any application assigned to the file types, or text editor, or viewer, etc

It looks like the environment variables (path-?) are broken somewhere and Krusader cant find itself. There is the lot of free space on my HDD, so that repeating error "at least 10547296 bytes" message is irrelevant.

The environment: Mac OS 10.7.5 (11G63) Darwin 11.4.2 on Mac mini Mid 2011 i7, XCode 4.6 (2066) + Instruments 4.6 (46000), MacPorts 2.1.3, Krusader compiled and installed with no errors.

[andrabr@…]

Same problem on Mountain Lion 10.8.3, Xcode 4.6.2 (4H1003).

I have documented a workaround here: ​http://n0tablog.wordpress.com/2013/05/05/instaling-krusader-orthodox-file-manager-on-mac-os-x-mountain-lion/

However, the workaround is far from perfect as a number of features, namely Root Mode Krusader, elude me.

I would be happy to provide extra info - just let me know what and how :-) Thank you.

[mastak365@…]

Thanks for sharing your workaround, andrabr. Forgive my nubeness, you suggested:

First, create a plain text file (not a Pages document or a PDF) – i used the most excellent TextWrangler – containing the following:

#!/bin/sh

mypath= ' dirname "$0" '

$mypath/krusader

What should be "mypath" in your solution? Or, is the above lines the exact content of kru.sh as it should be?

Did not work for me at all :( if I try to run the script I get same behaviour, the krusader icon shows up in the dock, jumps there for several times an disappears. Same as if I ran the krusader executable file. But, I got something new now: if I create the alias for the krusader binary file and run it instead I get it working with the extra terminal window where I can observe all those mentioned errors.

Also, I forgot to mention that my MAC is a member of Microsoft domain, hence the paths seem intricate. I figured it by right-clicking on the krusader binary and choosing “Show Package Contents” as you advised. This location seems to be something different from where I copied the script to, even though in the terminal window I cd-ed to the exactly same path chain... very odd to me.