Today I tried to update my CachyOs install and it failed, breaking up my system at the same time.
Here is a screenshot (sorry, unable to copy paste the terminal anymore) of the kind of errors I’m getting. This screenshot is not from the first failing command but it looks very similar being about a png file and truncated tar (the first time it was related to the brave browser package)
After the first error I decided to restart my computer, as the message states “no packages were upgrated”, I hoped I would find my system the way it was before I tried to update.
I noticed that on the boot screen I was not asked about launching CachyOS but Linux LTS, as it was my only option I went with that. First thing I noticed was the screen resolution that was not correct, and it is now impossible to change it.
I tried to reinstall all packages from CachyOS Hello, which gives me the following error
The Refresh keyrings from CachyOS Hello gives the following error:
Error : The keyring file /usr/share/pacman/keyrings/python-proton-linux.gpg does not exist
For now the computer is still booting, but I know that if I keep trying to update it will continue to fail and at some point not allow me to boot anymore, as it is exactly what happened last week.
If anyone have an idea on how I could fix that I’d be very gratefull.
Let me know if I can provide additionnal usefull info
The key is you see packages were removed (before being rebuilt), at that point you shouldn’t turn your pc off or reboot, but should instead take actions to rectify it.
Perhaps simply removing electron (temporarily) is the easiest solution or forcing it to overwrite the file would also be a valid action.
(opinion)dkms modules are a bit dodgy like that (I had zfs modules prior and issues, and am glad that Cachy builds the kernel with it baked in now).
There is a nice utility called cachy-chroot on the installation media that can easily get you inside your installation and then its usually just need to install / reinstall the failed packages.
@SphinxEffect Thx but I already re-installed last week and now having the same issue again. I’d like to understand what’s wrong to avoid re-installing next week ^^
I’ve managed to fix the keyring issue by removing all the packages related to proton (vpn, mail, …)
Now I am able to run the command to re-install all packages again, just got the same issue on another package this time:
Could not extract /usr/lib32/libLTO.so.19.1 (Truncated tar bla bla)
@inffy I’ve manage to chroot in my install last week while I was struggling so I guess it’s possible, but as for re-install I don’t want to deal with that kind of stuff on every update so I have to figure out what’s the issue in the first place
@naim Thank you, I’ll try to provide more context next time
the keyring issue was indeed solved by removing all proton packages
Is sudo pacman -Scc the same as Clear package cache from CachyOS Hello ?
Yesterday I tried to re-install at first with KDE and was able to get it running after a few failed installs but could not play on steam.
I’ve had a few failed attempts with Gnome and gave up for the night.
Today with the new release I was able to make a clean install with Gnome without any failed attempt !
No Man’s Sky on steam could not pass the first logo screen but works fine with Proton Experimental instead of proton cachyos (which was already the case on my previous install)
I’ll keep my install to a minimum until the next updates and I won’t have the same issue again !
I won’t have the same issue again !