Hi all- Linux newbie, sorry. Help & patience appreciated.
I can no longer get to the desktop (GNOME) of my Leap 15.2 system. There are several messages of “Failed to start Network Manager” followed by a loop of “Failed to start Login Service”.
I recently attempted to update all packages using zypper. The YaST GUI updater kept getting stuck on one (of ~500) updates with a dependency conflict.
zypper aborted since root was full. That was caused by a corrupt database (plexmediaserver). I Deleted the db files and rebooted
Here are the last steps taken:
Attempted to update packages using YaST GUI updater - failed due to a compatibility conflict
Attempted to update using zypper ref followed by zypper update
zypper aborted: root part full
deleted plexmediaserver’s corrupt / excessively large db files to free space
reboot → login failure
I assume this must be down to zypper installing some updates (but not all).
I’ve tried all 4 kernel options in GRUB to no avail.
Do I:
get to a shell and try to roll back / repair the updates? How?
OK, phew: I was able to use one of the “read-only snapshots” to get it to boot & login successfully. I chose one of the snapshots not marked zypper at the end (pkgkit, maybe? really should have written that down).
Per the docs, if everything with this snapshot checks out, I would just need to run
sudo snapper rollback
from the active snapshot to revert the “default” state back?
And if I understand correctly, data is preserved; will this affect e.g. the state of MariaDB databases?
I would advice to upgrade to 15.3 asap. It will become more and more difficult to get software for 15.2 and no updates for the OSS and non-Oss pacakages are offered anymore (since the begin of this month January).
Thanks Henk, will do. Given experience with zypper I think I’ll try the offline upgrade after attempting a rollback to stabilize things. Not that this was in any way the package manager’s fault. The offline upgrade docs reference 42.1 but assume the process is largely the same for Leap.
And answering my own question: no, things like databases, user data etc. are not affected b/c snapper excludes them by default. Good thing it was designed by smart people to help people like me
Just reporting back. The snapper rollback worked perfectly
The initial upgrade attempt (from USB/iso) got stuck on a black screen, did not catch what the last successful load was.
But tried it again last night and it completed successfully. I did have it connect to configured repos and it updated a bunch of media-related codecs (gstreamer etc.).
Interestingly in the upgrade setup it was much easier to tell it how to resolve conflicts vs. the YaST updater. YaST kept telling me “there’s a conflict” but the only option seemed to be to skip that update (after finding it in a long list of package updates). I probably missed how to do that properly with the YaST GUI updater.
I did not yet run zypper dup or zypper up but the GNOME updater says all is up to date. Should I?
Did you check for the extra repos as I mentioned above?
And doing a zypper up now is the best way to check if there are updates. Use the desktop update icon only as a “maybe I should check” indication. i have removed it in my KDE (in fact from the system).
