-
Notifications
You must be signed in to change notification settings - Fork 57
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
Problem with Pika Backup #198
Comments
Sounds like we might need to add a fuse thing to the image. I've been meaning to try pika anyway so I'll take a look, but if someone knows the packages we need off hand please leave a comment. |
Hi, |
uBlue doesn't remove a lot of packages (see packages.json). I think this is probably a difference between the official Fedora images and the testing ones we build ours on. |
Nice, thanks for your answer. |
Fedora won't have regular images until F39 which is why we're using their test images, see #78 for more info! |
Nice, thanks you a lot, it makes a lot of sense. |
Hi,
On a vm with fedora workstation 38, I don't have this error message (even though I have another one about Permission Denied, but probably related with my config). |
I am able to connect to things and make backups, but I am unable to confirm getting that fuse error, what steps are doing to get that error? thanks! |
I had some errors in my flatseal configuration, everythings work well now. |
Hi,
I try to use pika backup (from flathub) with the latest universal blue gnome.
When I try to mount an archive, I have an error message : fuse : device not found, try 'modprobe fuse' first.
If I type modprobe fuse in a terminal, I still have the error.
I have write a bug report on the Pika bug tracker, but the dev told me that the issue probably arise from the distribution.
So, I open a bug here, and will also try to do it on the silverblue bugtracker.
So far, I have also try to disable temporary selinux, and it didn't help.
Bug is very easily reproducible, you just need to mount an archive with Pika.
Thanks you!
The text was updated successfully, but these errors were encountered: