[Bug 1744168] Re: Lock to Launcher doesn't work for paths containing spaces

2018-01-21 Thread Khurshid Alam
Executable can only placed in either /usr/bin, /usr/local/bin or /$HOME/bin. None of that contains spaces. -- 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

[Bug 1744168] Re: Lock to Launcher doesn't work for paths containing spaces

2018-01-20 Thread Igor Mikushkin
Hmm... Khurshid, do you mean that executable cannot be placed into directory containing spaces? If that's the case I would prefer the library to report an error rather than creating ill-formed file. Or maybe it should be checked in Unity. Or maybe both. But silent creation of such a file looks

[Bug 1744168] Re: Lock to Launcher doesn't work for paths containing spaces

2018-01-18 Thread Khurshid Alam
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1744168] Re: Lock to Launcher doesn't work for paths containing spaces

2018-01-18 Thread Igor Mikushkin
** Also affects: bamf 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