Replies: 2 comments 4 replies
-
Yeah, it's a know issue with Fuse. Did you try anything from here? https://github.com/AppImage/AppImageKit/wiki/FUSE |
Beta Was this translation helpful? Give feedback.
-
Well, it's now working, but I don't know what I did to fix it. I tried all sorts of stuff I found in various posts, mostly on the CachyOS forum, and none of them did anything, until I rebooted. So presumably something's worked but a reboot was required to activate it. Installing fuse2 seems to be a common suggestion, and python-fuse. Some posts suggest installing appimagelauncher. I tried it but I didn't like it. I've used Gearlever to manage appimages on other distros and it works very well. Whether or not it installs anything that helps run appimages I don't know, but maybe?... Could be worth a shot. But you're right, it seems to be a very common problem. Hopefully it will get resolved. It should be as fuse is apparently required to run any appimage. ;-) Ian |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As the heading says. I'm looking at changing over to CachyOS as it is orders of magnitude faster than my current install, but I can't get NW to start. It keeps telling me that
fuse: memory allocation failed
. I also can't extract the binary from the appimage with the --appimage-extract option, it returnsthis doesn't look like a squachfs file
error.This seems to be a fairly common problem around the traps, not only NW and not only Arch. NW appimage works fine on my Fedora based linux (Aurora) and Mint, and I have other appimages working fine in CachyOS, so it seems to be to do with running NW on Arch. Just wondering if anybody else is having this problem, and if so did you fix it, and if so, how?
I've tried all the solutions I could find in other posts about this problem (although none involved NW) and nothing has worked.
All advice gratefully received.
Beta Was this translation helpful? Give feedback.
All reactions