Mass upgrade for OM Lx Rolling branch

Tags: #<Tag:0x00007fe3288c2ec8> #<Tag:0x00007fe3288c2db0> #<Tag:0x00007fe3288c2c70>

There has been another mass upgrade for OM Lx Rolling branch. Basically this happens when developers deem changes they have made in our development branch Cooker to be tested and stable enough to provide a stable usable system for users. This upgrade come with OM kernel-release-5.8.5-1.

The procedure for this upgrade is basically the same command you should use for daily or weekly upgrades:

Tips from Dr. Obokovsky

Rolling (and Cooker) users should not use Discover or dnfdragora to upgrade their system. This can result in bad things happening, maybe even a broken operating system. Instead open Konsole and use the following command:

$ sudo dnf clean all ; sudo dnf --allowerasing distro-sync

However there are 4 known issues with this upgrade.

  1. New issue: OM developers have split plasma-workspace-x11 and plasma-workspace-wayland in to separate packages. This allows users to install which ever they prefer and remove the one they don’t use or to have both. That is up to you. The issue here is that the ‘dnf distro-sync’ will (using alphabetical order) install only ‘plasma-workspace-wayland’ by default. If you happen to prefer x11 the you will need to manually install:

    $ sudo dnf install plasma-workspace-x11

    and keep or remove ‘plasma-workspace-wayland’ at your discretion.

  2. Old issue: If a Rolling user already has the same kernel version as the kernel provided in the upgrade then the kernel script will remove the /boot/initrd and user will not have a boot-able kernel. So if you know you have kernel 5.8.5 installed then boot in to an older kernel for this upgrade. That solves that. If you forget then boot in to another kernel, remove kernel 5.8.5 and run the upgrade command again.

    Note: Most Rolling users will have kernel 5.8.3 or older so this won’t matter in that case. This is included because kernel 5.8.5 was in Rolling main/testing repository just in case in one out there is affected.

  3. Existing/ongoing issue: Wifi users when you boot in to your system after the upgrade you will have to reset your wifi password. And there is some bug in something that is requiring user to enter password twice. Granted this is not much of an issue. I’ve heard speculation this issue might be caused by networkmanager itself, or kwallet, or systemd but have seen nothing really confirmed. Anyway this is easy enough to deal with.

  4. After upgrading you may see Discover updater applet wanting to upgrade or downgrade a few packages. This is because for some reason packagekit is not in sync with dnf. To get rid of this is very easy. As user run:

    $ pkcon refresh force

    and that will force packagekit to get in sync with dnf.

1 Like

For other known issues with rolling the list of most major open bug reports is here.

What is left out of that list are a lot of “package requests” and some reports that seem difficult to interpret what original poster is getting at.

1 Like

I have successfully done this upgrade (actually distro-sync) on znver1 and x86_64 hardware systems and also znver1 and x86_64 VirtualBox VM’s.

1 Like

Note: After an upgrade like this if user does not want to have a bunch of outdated duplicate packages it is helpful to use this command:

$ sudo dnf autoremove

In case of today’s upgrade it will remove a lot of lib64llvm, lib64clang, lib64opencv and a few others. However ‘autoremove’ can remove packages you might want or need to keep so pay attention. If you have any question or doubt don’t hesitate to ask us.

If you see a package in the autoremove list you want to keep that can be done with this command:

$ sudo dnf mark install <package_user_wants_to_keep>

1 Like