Skip to content
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

Closed
Froggy232 opened this issue May 11, 2023 · 9 comments
Closed

Problem with Pika Backup #198

Froggy232 opened this issue May 11, 2023 · 9 comments
Labels
help wanted Extra attention is needed

Comments

@Froggy232
Copy link

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!

@castrojo
Copy link
Member

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.

@castrojo castrojo added the help wanted Extra attention is needed label May 11, 2023
@Froggy232
Copy link
Author

Froggy232 commented May 11, 2023

Hi,
I can confirm that everything work on fedora silverblue 38, so it's probably some package that have been removed in universalblue.
Thanks you

@xynydev
Copy link
Member

xynydev commented May 12, 2023

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.

@Froggy232
Copy link
Author

Nice, thanks for your answer.
Just by curiosity, does someone know why we are based on the testing image and not the regular one?

@castrojo
Copy link
Member

Fedora won't have regular images until F39 which is why we're using their test images, see #78 for more info!

@Froggy232
Copy link
Author

Nice, thanks you a lot, it makes a lot of sense.
I suppose mounting archive through pika will not work until we switch to the official image, so fedora 39?
Thanks you

@Froggy232
Copy link
Author

Froggy232 commented May 13, 2023

Hi,
I just see that pika also doesn't connect to remote server, like borgbase one.
It throw me an error message : "Remote : ssh : could not resolve hostname XXX temporary failure in name resolution"
So far, I have tried to :

  • Disable the firewall
  • Disable selinux
  • Change DNS
  • Try another connection

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 think this is also a problem related to universal blue, I will test with a fedora silverblue VM.
Thanks

@castrojo
Copy link
Member

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!

@Froggy232
Copy link
Author

I had some errors in my flatseal configuration, everythings work well now.
Problem wasn't related to universal blue, sorry for the ticket.
Thanks you a lot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants