https://bugs.kde.org/show_bug.cgi?id=487927
--- Comment #2 from Emmett Culley <lst_man...@webengineer.com> --- Normally I use the launcher edit dialog. I enter a path to a script and save, and it works as expected. However, if the path include ~ I get a "Could not find program ~/bin/script_name". If it then edit the .directory file and remove the single quotes the launcher edit process added and save. Then the launcher doe work as expected that the script ~/bin/script_name does run. I only mention adding single quotes because I noticed that old launcher files on my system do not have that single quotes added and they still work. Since my upgrade to fedoraa 40, some no longers worked and in all cases I found single quotes around the script spec. I see two issues. One that some upgrade started adding single quotes to the script spec on launcher edit save. That caused no propblem, as all launchers still worked. But since upgrade to fedora 49 and KDE to 6, launchers script specs with a ~ no longer work. Unless I remove the single quotes from the launcher .directory file. Hence my suspician that what changed is bash expansion on the launcher script spec failes to translate ~ to my home directory. All I have to do to see this issue is right click on any launcher, alter the Program spec in anyway and save. the spec in the .directory file will now be wrapped in single quotes, even if it didn't before. If the spec contained a ~ then the launcher no longer works. I hope this helps. -- You are receiving this mail because: You are watching all bug changes.
