-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
Update of Packages and system failing. #1239
Comments
You have two separate issues here, one is a corrupt file when you do rpm-ostree update, another is a corrupt file when you do a flatpak update. This could be a network issue, a memory issue, or a drive issue. You might try doing a flatpak repair and clearing the cache via rpm-ostree. If these issues come back you have something more serious going on. |
Okay so here is what I have tried thus far.
So I tried After doing some additional research, I tried At this point while copying the output from that command to a text file to attach; the terminal crashed so lost the initial output from the cleanup command. However I ran
I thought okay maybe it just needed some time and tried
Looks good, I guess, let's try ccomer@main-bazzite:~$ ujust update
At this point, I'm at a loss, I'm going to reboot attempt everything again to see if I get different results. |
It appears that sudo flatpak repair worked this time.
I'm going to try a second reboot before attempting the update or flatpak update via Discover again just to be safe. |
After some weird reboots and kde have some odd display issues, I rebooted into the 1 option in the Grub Menu. This got me to what appeared to be a stable image (even though the versions listed on both the 0 and 1 options are the same). Discover showed the same packages as needing updated. This time I tried Now to figure out how to force Bazzite to boot the 1 option from Grub rather than the 0 which appears to have borked KDE. |
0 is your latest deployment, you can select the previous one with |
Thanks. I figured it out. I mainly just wish I knew what is causing this to begin with. |
Okay, I had some time after work. First, flatpak updates from Discover worked fine. However, upon attempting a System update to check if it is still having issues:
|
I had some time to dig into this some tonight. Did some research that pointed me to using ostree fsck to identify errors in certain commits. So what follows is my results thus far: TLDR version: I'm struggling to figure out how to proceed from here. The results I get when searching seem to refer to this issue when someone is writing software, not running a terminal command. Complete "transcript" below:
|
Describe the bug
First attempted to update 4 packages requiring updates via Discover.
![image](https://private-user-images.githubusercontent.com/112912804/340175230-524f23f8-4793-4413-b140-d2c37ed00029.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3ODMzOTgsIm5iZiI6MTcxOTc4MzA5OCwicGF0aCI6Ii8xMTI5MTI4MDQvMzQwMTc1MjMwLTUyNGYyM2Y4LTQ3OTMtNDQxMy1iMTQwLWQyYzM3ZWQwMDAyOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYzMFQyMTMxMzhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mNGFlODQ5NmZmM2RiYTVlOGFiZTRiNmVmNTExZmM5NjdjMmZhNGY3MjRlNmE2MDA3ZTQzYzI4YWE0MGFiNzQzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.c6nOiB2W1YMFgxbpXczIFyGqHc2hSuesF07LqAIGD9s)
All 4 updates failed with the following error codes.
Aborted due to failure (While pulling runtime/org.freedesktop.Platform.GL.default/x86_64/22.08 from remote flathub: opcode close: Corrupted file object; checksum expected='ce70fd8dc1e4846798673264ca1af30c33410d54046c05e6a5e30c4424cc416c' actual='ac1d008566082267a54a728ed35e6292fd5de61df22fd69cdaa5c6e0b4e0b058')
Aborted due to failure (While pulling runtime/org.freedesktop.Platform.GL.default/x86_64/22.08-extra from remote flathub: opcode close: Corrupted file object; checksum expected='ce70fd8dc1e4846798673264ca1af30c33410d54046c05e6a5e30c4424cc416c' actual='ac1d008566082267a54a728ed35e6292fd5de61df22fd69cdaa5c6e0b4e0b058')
Attempted update via command line with ujust update. Received the following error:
What did you expect to happen?
Expected either the Discover app to successfully update the packages in question or for the ujust update command to do so.
Output of
rpm-ostree status
Hardware
Operating System: Bazzite 40
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.8.12-301.fsync.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT
Manufacturer: ASUS
Asus Crosshair Hero VIII Wifi
Installed Main Drive: Samsung SSD 970 EVO Plus 2TB NVME (no SMART errors)
BIOS: 4805
Secure Boot: On (despite what Info Center claims)
Extra information or context
No response
The text was updated successfully, but these errors were encountered: