The Cursor-0.48.9-x86_64.AppImage has no icon and cannot be opened
Pre-submit checks
- [x] I checked for similar issues beforehand, but could not find any, not even closed ones. I could not add my bug report to any existing issue.
- [x] I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.
Describe the bug
I upgraded from 2.0.0 to Release v3.0.0-alpha-4, but the cursor icon cannot be displayed correctly. What should I do? And I can open the cursor appimage file directly, but I can't open the cursor file generated by AppImageLauncher.
Expected behavior
The cursor icon is displayed correctly
Steps to reproduce the issue
No response
Screenshots
Distribution and desktop environment
ubuntu 24.04 gnome
Installed AppImageLauncher version
appimagelauncher_3.0.0-alpha-4-gha253.36951ec_amd64.deb
List of AppImages you tried
appimagelauncher_2.2.0-travis995.0f91801.bionic_amd64.deb
Additional context
No response
I am having the same issue. If you just delete the highlighted part from the desktop entry, it works. I have been just doing that after each update. By the way, the issue isn't just cursor related. I am having the issue on other apps as well.
if this gets merged (maintainer u will have to fix my shit code) --- you will get a cursor icon libappimage is in appimagelauncher and is the part responsible for importing the icons etc.
https://github.com/AppImageCommunity/libappimage/pull/198
The issue with cursor as i understand it is that it can't run within a sandbox:
https://forum.cursor.com/t/cursor-install-ubuntu-24-04/4838
and you need to explicitly append the --no-sandbox option when executing the AppImage, which breaks security.
Just hitting this with multiple apps - no icons being created.
and you need to explicitly append the --no-sandbox option when executing the AppImage, which breaks security.
Most AppImages have that in their desktop file, actually. It's because Electron apps ship with a complete browser which can access resources from the Internet, too. Sometimes it can be worked around with user namespaces. But we cannot do anything about it. You need root rights to set suid on a binary, after all.