Bug 461064 - Execute as a default behavior when opening a script
Summary: Execute as a default behavior when opening a script
Status: RESOLVED INTENTIONAL
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-27 11:28 UTC by mnonw742710
Modified: 2022-10-28 17:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mnonw742710 2022-10-27 11:28:37 UTC
Having confirmation dialog confusing to new user
The executable permission and open with context menu is already doing this job for most people
Having a "do not ask again" doesn't help much either
Let's say, if the user click open the first thing they see is a confirmation dialog
Like most people having to do it everytime they run something on his own computer sound annoying
they will click the "do not ask again" checkbox as a next step
because most people read left to right user will see "open" first and think "open" has the same meaning
as "run" or "execute"
the file will open in a text editor, the user is confused and next
the user will search for a solution and find out than in order to run a script you have to enable execute permission
the user open properties dialog and found out that the executable permission is already enabled
the same user will again search for a solution and find out that he have to set the behavior for script execution as open
for a first time setup this behavior consist of too many steps
This is a nice feature as I'm using it myself but i think it should be opt-in and remove the "do not ask again" checkbox along with it if the former was possible would be a great addition
Comment 1 Nate Graham 2022-10-28 17:38:14 UTC
This would leave the system vulnerable to exploitation by malicious files by default. For that reason, asking for confirmation by default is intentional. Most users don't run script files and executables manually; if you are one such user and you're comfortable with the risks of executing by default, you're welcome to make use of the setting to do so.