Those files may be executable and the user wants them to execute. For example:
- Shell scripts the user has written to perform commonly-used actions
- Windows executables opened with WINE
For this reason, we should stop explicitly blocking running executable files when accessed with KRunner runners or Kicker/Kickoff/Application Dashboard, and instead show the typical "open or execute?" dialog that respects the user's setting for what to do in this case.
BUG: 455924 FIXED-IN: 5.26