Bug 308553 - -e (execute) option mishandles spaces
Summary: -e (execute) option mishandles spaces
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.9.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: reproducible
Depends on:
Blocks:
 
Reported: 2012-10-17 14:29 UTC by Daniel Faust
Modified: 2012-11-01 10:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 4.9.3


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Faust 2012-10-17 14:29:17 UTC
It seems to be impossible to start konsole with a file to be executed that contains one or more spaces.
Starting such a file via a .desktop file ("execute in a terminal window" option checked) won't work either but it's probably the same bug.

The bug is being tracked on launchpad as well: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/948321

Reproducible: Always

Steps to Reproduce:
execute something like:
konsole --noclose -e /media/Serien\ 3TB/backup_worker.sh
or
konsole --noclose -e "/media/Serien 3TB/backup_worker.sh"
Actual Results:  
The following message gets displayed in the terminal where the command was started from:
konsole(3645): "Programmdatei kann nicht gefunden werden: " "/media/Serien"
[konsole(3645): "Program file cannot be found: " "/media/Serien"]

And these messages get displayed in the newly started konsole window:
Achtung: „/media/Serien“ kann nicht gefunden werden, stattdessen wird „/bin/bash“ gestartet. Prüfen Sie bitte die Einstellungen des Profils.
[Warning: „/media/Serien“ cannot be found, „/bin/bash“ will be started instead. Please check your profile settings.]
3TB/backup_worker.sh: Datei oder Verzeichnis nicht gefunden
[3TB/backup_worker.sh: File or directory not found]
Comment 1 Kurt Hindenburg 2012-10-27 02:55:19 UTC
Yes, konsole separates the program and args by spaces.
Comment 2 Jekyll Wu 2012-11-01 05:43:57 UTC
The problem should be fixed by http://commits.kde.org/konsole/48b5575c174fb4edb6d3388d7a22dec148dea8cb and http://commits.kde.org/konsole/e48cee6cca742a5bdb3daf6fa0b7c76073217faa . If lucky, the fix should catch KDE 4.9.3.
Comment 3 Daniel Faust 2012-11-01 10:41:53 UTC
I can confirm the fix. Thank you.