[kde] [Bug 499589] New: Attempting to run an AppImage that needs a --no-sandbox from UI just exits without helpful message
Reuben
bugzilla_noreply at kde.org
Thu Feb 6 11:38:06 GMT 2025
https://bugs.kde.org/show_bug.cgi?id=499589
Bug ID: 499589
Summary: Attempting to run an AppImage that needs a
--no-sandbox from UI just exits without helpful
message
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: kde at flavor8.com
Target Milestone: ---
SUMMARY
This is from Dolphin, but presumably the issue is deeper in KDE.
I can run a downloaded AppImage from Dolphin - when I double click, it pops up
a dialog asking if I want to execute it. However, if the AppImage is electron
and needs to mount the chromium sandbox(??), nothing will visible happen after
clicking "execute". This is suprising and annoying.
KDE should detect this situation, and give a choice (presented in a more
explanatory way):
a) Sudo to fix the perms on the sandbox
b) Run without sandbox
STEPS TO REPRODUCE
1. Download Quiqr AppImage (https://quiqr.org/)
2. Attempt to run it from Dolphin
OBSERVED RESULT
Nothing apparently happens, as described. Per Claude, the two alternatives are:
1) Run the AppImage with the --no-sandbox flag:
./your-appimage.AppImage --no-sandbox
2) Set the correct permissions as root:
sudo chown root:root /tmp/.mount_quiqr_huIfd2/chrome-sandbox
sudo chmod 4755 /tmp/.mount_quiqr_huIfd2/chrome-sandbox
./your-appimage.AppImage
EXPECTED RESULT
Containers (hopefully including AppImages) are part of the future. KDE should
help remove the friction of using them.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-13-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 30.6 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUS
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list