Package: launchy Version: 2.5-3 Severity: minor Tags: upstream Dear Maintainer,
it looks like Launchy has problems to launch complex commands from desktop files. Namely, I have experience these problems: 1) Having a desktop file with Exec definition pointing to home directory using tilda - e.g. Exec=~/bin/script_name, Launchy is unable to launch the command (simply hitting Enter on the found item from the list does not trigger any action). PS: typing ~/bin/script_name directly in the Launchy window, the script is started. So the problem really seems to be only when combined with a desktop file. 2) If Exec in a desktop file contains sequence of commands separated by semicolon, Launchy only runs the first command. Although I have to admit I am not sure whether such an Exec is not against desktop file specifications, it looks like other launchers treat this correctly. Thanks, Pavel -- System Information: Debian Release: stretch/sid APT prefers testing-proposed-updates APT policy: (840, 'testing-proposed-updates'), (840, 'testing'), (740, 'unstable'), (738, 'experimental'), (540, 'proposed-updates'), (540, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages launchy depends on: ii libc6 2.19-20 ii libgcc1 1:5.2.1-17 ii libqt4-network 4:4.8.7+dfsg-3 ii libqtcore4 4:4.8.7+dfsg-3 ii libqtgui4 4:4.8.7+dfsg-3 ii libstdc++6 5.2.1-17 ii libx11-6 2:1.6.3-1 launchy recommends no packages. Versions of packages launchy suggests: ii launchy-plugins 2.5-3 ii launchy-skins 2.5-3 -- no debconf information
