When I call `desktop-launch /', I get the following warnings: /usr/bin/desktop-launch: line 321: test: : oczekiwano wyrażenia całkowitego /usr/bin/desktop-launch: line 322: test: : oczekiwano wyrażenia całkowitego /usr/bin/desktop-launch: line 323: test: : oczekiwano wyrażenia całkowitego The reason is that kde-config is gone. The following patch fixes the problem. *** /usr/bin/desktop-launch 2009-10-24 05:26:39.000000000 +0200 --- /tmp/ksocket-krzysztof/desktop-launch 2010-05-23 13:56:38.622084191 +0200 *************** detectDE() *** 314,320 **** kfmclient_fix_exit_code() { ! version=`kde-config --version 2>/dev/null | grep KDE` major=`echo $version | sed 's/KDE: \([0-9]\).*/\1/'` minor=`echo $version | sed 's/KDE: [0-9]*\.\([0-9]\).*/\1/'` release=`echo $version | sed 's/KDE: [0-9]*\.[0-9]*\.\([0-9]\).*/\1/'` --- 314,320 ---- kfmclient_fix_exit_code() { ! version=`kde4-config --version 2>/dev/null | grep KDE` major=`echo $version | sed 's/KDE: \([0-9]\).*/\1/'` minor=`echo $version | sed 's/KDE: [0-9]*\.\([0-9]\).*/\1/'` release=`echo $version | sed 's/KDE: [0-9]*\.[0-9]*\.\([0-9]\).*/\1/'`
But xdg-utils should keep compatibility with KDE<4
2 things. xdg-utils support for kde4 should be quite good in cvs now. we probably need to do a release soon, to get this into the hands of users. I don't see any mention of 'desktop-launch' anywhere in xdg-utils. ???
(In reply to comment #2) > 2 things. > > xdg-utils support for kde4 should be quite good in cvs now. we probably need > to do a release soon, to get this into the hands of users. > > I don't see any mention of 'desktop-launch' anywhere in xdg-utils. ??? /usr/bin/desktop-launch: symbolic link to `xdg-open' (provided by desktop-data-openSUSE-11.2-10.1.noarch)
(In reply to comment #1) > But xdg-utils should keep compatibility with KDE<4 How about this code? version=`{ kde-config --version || kde4-config --version; } 2>/dev/null | grep KDE`
ok, the rest of the kde4 support is already included in cvs then.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.