Bug 467663

Summary:	Execute .desktop files from program:/
Product:	[Frameworks and Libraries] frameworks-kio	Reporter:	federico
Component:	general	Assignee:	KIO Bugs <kio-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kdelibs-bugs-null, kfm-devel, p.r.worrall
Priority:	NOR
Version First Reported In:	5.104.0
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description federico 2023-03-21 20:44:12 UTC

SUMMARY

When double-clicking on a .desktop file from the "program:/, view/protocol I would like to execute the registered program instead of opening the desktop file with kate.


STEPS TO REPRODUCE
0. (optional) Verify that the setting "When opening an executable file:" is set to "Always ask" or "Run script"
1. Got to programs:/Internet/
2. double-click on firefox (or another browser)

OBSERVED RESULT
firefox.desktop is opened in the configured text editor (Kate in my case)

EXPECTED RESULT
When opening the "programs:/" view, I expect to be able to execute programs just like it happen when clicking on a icon in the menu.

I expect this behavior not to depend on the setting "When opening an executable file", as .desktop files are not necessarily executable, but the current behavior makes the "programs:/" view unusable.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-6-amd64 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

Comment 1 federico 2023-03-21 20:48:10 UTC

Update: also not that while not useless, opening a desktop file with the editor from the "program:/" view is confusing, because if you want to edit it, you cannot save the changes.

In Kate the "save" button does nothing, and when closing the file and saving on close I get the following error:

"Data you requested to be saved could not be written. Please choose how you want to proceed."

I've tested it with a desktop file located in ~/.local/share/applications, so it is not a permission issue.

Comment 2 Paul Worrall 2023-03-22 09:44:15 UTC


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