AppImage does not launch. I tried both directly running it, and integrating it with Gear Lever (see issue).
The app should launch
chmod +x aspect-1.0.0-rc.3-x86_64.AppImageFedora 41
GNOME 47
Wayland
Linux kernel 6.11.8-300.fc41.x86_64
If you run the app image from a terminal, do you get any error output. We still have the issue that the AppImage requires FUSE2 to run. For modern distributions that means that libfuse2 either needs to be installed manually, or the AppImage needs to be extracted with ./aspect-... --appimage-extract.
I’ll have another look, though, whether this can be made to work properly by now with the system we are using. Last time I’ve checked, we would have had to completely change the AppImage build process, which right now doesn’t really fit in the time budget.
Mmmmh, it’s very weird: if I try to run the file from terminal, I get zsh: no such file or directory: ./aspect.appimage, but I am sure the file name is correct, and it appears in ls -al…
I just tried on Linux Mint 22, with libfuse2 installed and running/installing with Gear Lever as worked fine there. After I removed libfuse2, Gear Lever did show an error message suggesting to install FUSE 2 or to extract the AppImage, so that is probably not the issue either.
So it looks like this might actually be some issue with Aspect itself. Can you have a look whether /tmp/aspect-log.sdl exists and paste/attach that here if it does?
Thank you for your help, @Soenke, but unfortunately still nothing…
I observe the same behaviour described above after running sudo dnf install fuse fuse-devel.
No /tmp/aspect-log.sdl file is created.
Still happening with aspect-1.0.0-rc.4-x86_64.AppImage
I installed Fedora 41 in a VM and tested it there. For me, everything worked flawlessly out of the box, both by making the AppImage executable and double-clicking, as well as using Gear Lever. In contrast to Ubuntu, it wasn’t necessary to install FUSE 2 libraries.
To hopefully get to the root of this, though, can you try to run the following commands in a terminal and see what the output is?
wget https://download.bildhuus.com/packages/aspect/aspect-1.0.0-rc.4-x86_64.AppImage
chmod +x aspect-1.0.0-rc.4-x86_64.AppImage
./aspect-1.0.0-rc.4-x86_64.AppImage
It’s crazy! This never happened to me before! 
wget https://download.bildhuus.com/packages/aspect/aspect-1.0.0-rc.4-x86_64.AppImage
chmod +x aspect-1.0.0-rc.4-x86_64.AppImage
./aspect-1.0.0-rc.4-x86_64.AppImage
aspect-1.0.0-rc.4-x8 100% [==================================================================================================>] 75.14M 5.77MB/s
[Files: 1 Bytes: 75.14M [5.50MB/s] Redirects: 0 Todo: 0 Errors: 0 ]
zsh: no such file or directory: ./aspect-1.0.0-rc.4-x86_64.AppImage
That looks really strange indeed. when you type ls -l aspect* afterwards, do you get any files listed?
For reference, this is what I get:
user@fedora:~$ wget https://download.bildhuus.com/packages/aspect/aspect-1.0.0-rc.4-x86_64.AppImage
chmod +x aspect-1.0.0-rc.4-x86_64.AppImage
./aspect-1.0.0-rc.4-x86_64.AppImage
aspect-1.0.0-rc.4-x8 100% [=============================>] 75.14M 8.59MB/s
[Files: 1 Bytes: 75.14M [9.13M]
Starting Aspect 1.0.0-rc.4
Command line arguments: ["./aspect-1.0.0-rc.4-x86_64.AppImage"]
Logical processors: 2 (HT=true)
Initializing SDL2...
(...)
Running ls -al I get this:
-rwxr-xr-x. 1 tommi tommi 78795968 Nov 30 20:10 aspect-1.0.0-rc.4-x86_64.AppImage
(user tommi is me)
Hmm, does this yield any output?
./aspect-1.0.0-rc.4-x86_64.AppImage --appimage-help
It’s really strange that the shell wouldn’t find the executable when it’s obviously there. By the way, do you have zsh set up as your default shell? For my vanilla installation it’s using bash and zsh isn’t installed.
Same… “file or directory not found”. 