Bug 428042

Summary: KRunner doesn't launch shell scripts anymore
Product: [Plasma] krunner Reporter: Nicola Mori <nicolamori>
Component: generalAssignee: Alexander Lohnau <alexander.lohnau>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nicolamori, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.20.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nicola Mori 2020-10-21 06:54:36 UTC 
SUMMARY
After updating my system to 5.20.0 KRunner doesn't properly recognize and launch shell scripts. In 5.19.5 and previous versions I could start with alt+F2, then type the path to an executable shell script (e.g. "~/scripts/myscript.sh") the suggested action was something like "Run script", and then pressing enter the script was executed. In 5.20.0 and 5.20.1, doing the same procedure the only suggested action is "Get GNU Image Manipulation Program" from the "Software center" plugin. Disabling the plugin, no action is suggested and nothing happens when pressing enter. The "Command line" plugin is enabled.

STEPS TO REPRODUCE
1. Open KRunner with alt+F2
2. type the address of an executable shell script file

OBSERVED RESULT
The proposed action is "Get GNU Image Manipulation Program" from the "Software center" plugin.

EXPECTED RESULT
The proposed action should be "Run script" from the "Command line" plugin.

SOFTWARE/OS VERSIONS
Linux: Archlinux
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Comment 1 Nicola Mori 2020-10-21 07:00:05 UTC 
I just found the problem: the "~" character. Writing the full path "/home/myuser/scripts/myscript.sh" KRunner behaves as expected. So the problem is in expanding the "~", that was done correctly in 5.19.5 but that stopped working in 5.20.0.
Comment 2 Alexander Lohnau 2020-10-21 07:02:04 UTC 
Sorry for that, the fix will be included in the bugfix release next week.

*** This bug has been marked as a duplicate of bug 427824 ***