Bug 433649 - Executable AppImage fails to open in Dolphin
Summary: Executable AppImage fails to open in Dolphin
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 20.12.2
Platform: Other ChromeOS
: NOR major
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-26 10:12 UTC by Fred Brigham
Modified: 2026-02-05 03:56 UTC (History)
2 users (show)

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


Attachments
Dolphin with AppImage file set to executable (377.75 KB, image/png)
2021-02-26 10:12 UTC, Fred Brigham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fred Brigham 2021-02-26 10:12:51 UTC
Created attachment 136187 [details]
Dolphin with AppImage file set to executable

SUMMARY
Executable AppImage fails to open in Dolphin

STEPS TO REPRODUCE
1. Install Dolphin from Flatpak
2. Check permissions using Flatseal
3. Attempt to execute an AppImage. The file is located in Home folder and checked as executable - see screenshot.

OBSERVED RESULT
Attempting to open AppImage results in error message "Unable to find an application that is able to open digikam-7.1.0-x86-64.appimage".

EXPECTED RESULT
It should be possible start AppImages by double clicking the relevant icon in the Home folder.

SOFTWARE/OS VERSIONS
KDE Plasma Version: Plasma desktop not installed
Linux: Debian Buster (v.10) / Crostini (on Chromebook) 

ADDITIONAL INFORMATION
Please note that Nemo works perfectly under the same conditions and the AppImage opens without any problems.
Comment 1 aristsakas 2026-01-03 21:40:57 UTC
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Dolphin 25.12.0.
Comment 2 Bug Janitor Service 2026-01-18 03:47:19 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Fred Brigham 2026-01-21 09:45:10 UTC
The bug report was left in February 2026, nearly 5 years ago! At that time I was running Linux on a Chromebook. I no longer have the Chromebook or Linux.
When I could no longer update my Windows 10 laptop I considered installing Linux Mint but decided to go over to Windows 11 on an Microsoft Surface laptop with an arm64 Snapdragon X Plus processor. Unfortunately Linux is totally confusing for the average user thanks to the various distros, as well as being unreliable thanks to the many bugs.
Comment 4 Bug Janitor Service 2026-02-05 03:56:05 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

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