Bug 416973 - Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable
Summary: Dolphin won't run binaries or scripts, even when set to always ask on opening...
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.66.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-31 04:28 UTC by Kyle Devir
Modified: 2020-03-01 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Visual of bug (492.76 KB, image/png)
2020-01-31 04:28 UTC, Kyle Devir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle Devir 2020-01-31 04:28:45 UTC
Created attachment 125564 [details]
Visual of bug

SUMMARY

Recently, I noticed that Dolphin was always complaining with "The file <such and such> is an executable program. For safety it will not be started.", even when Dolphin is set to always ask when I click an executable binary.

For scripts, it will just always open them in kate.

I decided to do some digging, and I think it might be caused by some odd bug in this commit:

2bb58858c8f6f37b82028bdbc86c19e9acfd71f2, "Added dialog to set execute permission for executable file when trying to run it.", author Marcin Dłubakowski<m.dlubakowski@gmail.com>

STEPS TO REPRODUCE
1. Set "Settings -> Configure Dolphin -> General -> Confirmations -> When opening an executable file:" to "Always ask" 
2. Set binary or script to be executable.
3. Click on binary or script in Dolphin.

OBSERVED RESULT

"The file <such and such> is an executable program. For safety it will not be started.", always.

EXPECTED RESULT

Dolphin asks whether I would like to execute or run the binary or script.

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1
Kernel Version: 5.5.0-arch1-1-custom
OS Type: 64-bit
Processors: 6 × AMD Ryzen 5 2600X Six-Core Processor
Memory: 15.6 GiB of RAM
Comment 1 Kyle Devir 2020-01-31 05:08:13 UTC
So... this issue was fixed by editing ~/.config/kiorc ... :/
Comment 2 Nate Graham 2020-01-31 19:06:38 UTC
What did you have to change in ~/.config/kiorc to fix it?
Comment 3 Bug Janitor Service 2020-02-15 04:33:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2020-03-01 04:33:20 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!