No automatic way to fix corrupted system files
Technically this should be an ostree related bug but I'll post it here first before doing a bug report
What I encountered was some system file corrupted, or at least I thought it was.
All system notification sounds just does not play anymore while audio from other applications play normally.
shows that there are corrupted files on the system.
unfortunately there are no way to automatically fix this.
I tried to use , as that seems to be the easiest way to fix this and I assumed rpm-ostree would just automatically pull the missing files.
It was a bad idea.
As seen from the screenshot, rpm-ostree really did not like it. Following a workaround from 2016 https://github.com/ostreedev/ostree/pull/345#issuecomment-262263824 also does not work.
I had an idea to pull the entire image by to try to fix it, but rpm-ostree complains that
To work around this, I am currently trying to rebase onto the nvidia image and then rebase back to the normal image.
GitHub
POC: fsck repair by krnowak · Pull Request #345 · ostreedev/ostree
This is something I quickly hacked up, since I haven't seen any possibility to tell ostree to fetch the missing objects after doing ostree fsck --delete.
For now it only tries to download c...
5 Replies
still encountering corruption
I've had ostree fsck report curroption on bazzite before as well. So have many other users. It seems to be related with ostree fsck not fully supporting OCI images , I am not sure , but your issue might not be related to the "curroption" at all
with this issue, rpm-ostree update will fail
only way to get it to go away is to rebase a different image and hope it refetches the thing
Yes do that
You can choose a stable tag it does not matter
Bazzite has some workarounds in it that may corrupt hashes