probonopd
Fuse error on latest build on Ubuntu 20.04. Build 823 works fine
With latest build I get following error
./appimaged-831-x86_64.AppImage
fuse: failed to exec fusermount: Permission denied
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
open dir error: No such file or directory
Previous build works without any other changes.
./appimaged-823-x86_64.AppImage
appimaged-823-x86_64.AppImage 177
2024/06/01 11:34:10 Desktop notification: Not running on one of the supported Live systems This configuration is currently unsupported but may still work, please give feedback.
-
-
-
This process based on /proc/self/exe: /tmp/.mount_appimaBkmLJC/usr/bin/appimaged
Terminating other running processes with that name...
In the future, would send SIGTERM to 31889
In the future, would send SIGTERM to 165259
2024/06/01 11:34:10 Deleted 51 desktop files from /home/USER/.local/share/applications/; use -v to see details
2024/06/01 11:34:10 Probably not launched by systemd (please file an issue if this is wrong)
2024/06/01 11:34:10 Manually launched, not by systemd. Check if enabled in systemd...
2024/06/01 11:34:10 /etc/systemd/user/appimaged.service does not exist
2024/06/01 11:34:10 Creating ~/.config/systemd/user/appimaged.service
2024/06/01 11:34:10 thisai.path: ~/Applications/appimaged-823-x86_64.AppImage
2024/06/01 11:34:11 /bin/systemctl --user status appimaged
2024/06/01 11:34:11 exit status 3
2024/06/01 11:34:11 Enabling systemd service...
2024/06/01 11:34:11 Starting systemd service...
2024/06/01 11:34:11 appimaged should now be running via systemd. To check this, run
2024/06/01 11:34:11 /usr/bin/systemctl -l --no-pager --user status appimaged
I have tried above scenarios 3 times even with system restart and results are same.
The changes at https://github.com/probonopd/go-appimage/compare/832...continuous shouldn't have caused this. So I suspect something got changed during build process.
I am on Ubuntu
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
What does ls -lh $(which fusermount) say? And what does ls -lh $(which fusermount3) say?
$ ls -lh $(which fusermount)
lrwxrwxrwx 1 root root 11 Mar 7 2020 /bin/fusermount -> fusermount3
$ ls -lh $(which fusermount3)
-rwsr-xr-x 1 root root 39K Mar 7 2020 /bin/fusermount3
It is working fine with 823.
I'll try with latest later today.
Same error
$ ./appimaged-833-x86_64.AppImage
fuse: failed to exec fusermount: Permission denied
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
open dir error: No such file or directory
Possibly related to https://github.com/AppImage/type2-runtime/pull/18?
Can you please download, make exectuable, and run (from the command line) the appimagetool AppImage from https://github.com/AppImage/appimagetool/releases? Do you get the same error there?
Exact same error
$ ./appimagetool-x86_64.AppImage
fuse: failed to exec fusermount: Permission denied
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
open dir error: No such file or directory
I fixed it by following clues from https://github.com/AppImage/type2-runtime/issues/15#issuecomment-1764673104
I tested first with setting FUSERMOUNT_PROG
It worked
Then comment https://github.com/AppImage/type2-runtime/issues/15#issuecomment-1771155097 helped.
Now I have setup symlink ln -s /bin/fusermount /usr/bin and it worked without any issues.
Possibly the same issue as https://github.com/AppImage/type2-runtime/pull/32#issuecomment-2192269868?
I can confirm:
- The original problem: '(...)Permission denied' when trying to execute
./appimagetool-x86_64.AppImagewith fusermount on /bin instead of /usr/bin with newer versions of go-appimage; - that it does not happen with v.823;
- that prefixing the command line with
FUSERMOUNT_PROG=/bin/fusermountworks around it.
I would like to add:
- The same problem ALSO HAPPENS with the .AppImage binaries generated using newer versions (more specifically 869), and also DOES NOT happen with the same binaries processed using v.823 (that is, this issue affects not only go-appimage itself, but also the .AppImage binaries generated using it).
For my use case, this really threw a wrench in the works with using newer versions, and forced me to downgrade to 823.
Is anyone working on having this fixed on the newest versions?
@DurvalMenezes Do you have the issue if you repackage the AppImage with this appimagetool?
It uses a slightly different runtime.
Sorry for the delay in responding. I do not use the original appimagetool because it totally fails to work in my use case (misses lots of libraries, etc).
https://github.com/AppImage/appimagetool does not even attempt to bundle libraries at all - it leaves that job to other programs, and just converts an already-existing AppDir into AppImage format.
Sorry for the delay in responding. I do not use the original appimagetool because it totally fails to work in my use case (misses lots of libraries, etc).
Use go appimage to deploy, but instead of turning the AppDir back into an appimage with go-appimage, use the other appimagetool.