Public bug reported:

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/share/applications
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-legacy-window.c from lp:bamf. But I don't know how
to setup testing environment and check it on my machine.

Ubuntu 17.04
libbamf3-2: 0.5.3+17.04.20170406-0ubuntu1

** Affects: unity
     Importance: Undecided
         Status: New

** Affects: unity (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  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/share/applications
  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-legacy-window.c` from lp:bamf. But I don't know how to setup 
testing environment and check it on my machine.
+ 
+ I guess the problem is that the result of get_exec_string is never
+ escaped in src/bamf-legacy-window.c from lp:bamf. But I don't know how
+ to setup testing environment and check it on my machine.
  
  Ubuntu 17.04
  libbamf3-2: 0.5.3+17.04.20170406-0ubuntu1

** Also affects: unity
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744168

Title:
  Lock to Launcher doesn't work for paths containing spaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1744168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to