Lock to Launcher doesn't work for paths containing spaces
Bug #1744168 reported by
Igor Mikushkin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BAMF |
New
|
Undecided
|
Unassigned | ||
Unity |
New
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1. Place an executable in the path with spaces
2. Start it
3. Lock to Launcher in Unity panel
4. Close it
5. Try to start it from panel
Expected results:
Application started
Actual results:
It cannot start
Manual fix:
1. You can open created the file from ~/.local/
2a. Manually escape spaces in Exec parameter
2b. Or surround this string with quotes
I guess the problem is that the result of get_exec_string is never escaped in src/bamf-
Ubuntu 17.04
libbamf3-2: 0.5.3+17.
description: | updated |
To post a comment you must log in.
Spaces in exec parameter is against free desktop specification. Also a script should not contain spaces in its name. You need to fix your code. Nothing to be fixed here.