-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Unable to mount Pika Backup archive #2193
Comments
I cannot replicate this on bluefin. I created a fresh backup of my home as a local backup and was able to browse the archive. |
Are you running the exact same version of Bluefin or something else? What does you |
I'm running stable instead of gts so that maybe a difference. This was tested while I was temporarily on bluefin-dx-nvidia. I personally use a downstream image based on bluefin. |
But on gts, are you able to replicate it? |
I have not tested on GTS. I will spin to a VM here shortly. |
@m2Giles, what other variations of my system could there be? |
Not sure what to recommend here. This should be pretty automatic. |
Can you see what logs you get in journalctl when trying to browse the archive? |
@m2Giles, this
|
No more logs around that time. Wondering if there is some sort of SELinux issue happening |
I rebased to |
Are you able to browse a local archive and this is an issue with remote archive? |
No, this is a local archive. Apologies, I should've said much earlier. |
Describe the bug
After performing a backup with Pika on Bluefin, I was unable to mount the archive and it says
What did you expect to happen?
The backup should mount as a browseable directory.
Output of
bootc status
Output of
groups
Extra information or context
According to the issue here
https://gitlab.gnome.org/World/pika-backup/-/issues/527#note_2344721
It works fine on plain Silverblue. Has a fuse dependency been removed?
The text was updated successfully, but these errors were encountered: