-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation needs to be updated for Ubuntu 22.04 / Fuse section #73
Comments
You are referring to this section? https://github.com/AppImage/docs.appimage.org/blob/master/source/user-guide/troubleshooting/fuse.rst#setting-up-fuse-2-x-on-ubuntu-debian-and-their-derivatives Would you like to send a pull request? |
Done #74 |
See what I meant? https://blog.shn.dev/using-appimages-on-ubuntu-22-04-comes-with-trade-offs/ P.S.: There should be modifications on the Wiki too https://github.com/AppImage/AppImageKit/wiki/FUSE |
There is a slight issue with this now. On the latest Ubuntu image, that is, downloaded couple of days ago, it can't locate the package libfuse2.
|
It's in root@e4fa719ae238:/# apt policy libfuse2
libfuse2:
Installed: (none)
Candidate: 2.9.9-5ubuntu3
Version table:
2.9.9-5ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages |
Thank you for the quick answer! May it be that universe is enabled by default on installed OS and disabled when running in live mode? Because I am running live USB now for some recovery purposes |
I think it is enabled by default for desktop installations only, actually. But I'm not sure. I'm pretty sure it is disabled on live media by default, yeah. |
The current instructions are not valid anymore and could lead to break the system.
'libfuse2' can live along fuse3 but we should not attempt to install the package 'fuse' nor to do all the rest with groups/modprobe...
Tested with a fresh 22.04, the only required step is:
sudo apt install libfuse2
If the users follow "blindly" the current instructions, they could think the format is responsible of the damages!
The text was updated successfully, but these errors were encountered: