An RPM dependency …
Same with me today with the update. Suddenly kernel-preempt got installed, where until now only kernel-preempt-devel was there, required by dkms to make virtualbox run.
I did sometimes try to do away with that kernel-preempt-devel, but yast warned me not to do that because dkms needed it.
And now today, suddenly, the whole kernel-preempt reappeared and took over my system. Just for a few minutes, because I immediately took action.
What I did is: UNINSTALL virtualbox-kmp-preempt AND kernel-preempt AND kernel-syms AND kernel-preempt-devel ; for the latter two, an older version remains installed.
Trying to actualize kernel-syms does not work because in that case, yast wants me to reinstall the unwanted kernel-preempt …
I have no idea why this kernel-preempt resurfaced just today.
Last time a VirtualBox update triggered a similar mess, please see post #4](https://forums.opensuse.org/showthread.php/549337-Is-it-normal-that-my-running-kernel-is-kernel-preempt-instead-of-kernel-default?p=2998552#post2998552)
I see now that virtualbox-6.1.18-lp152.2.18.1.x86_64.rpm has a timestamp reading April 11, so maybe the same problem time and again…
If you update just the kernel, then update just VirtualBox (and related KMPs) everything should work AFAIK (cannot check at the moment).
kernel-preempt-devel requires kernel-preempt. This appeared in the latest patch:
+-------------------------------------------------------------------
+Mon pr 12 14::20 CEST 2021 - tiwai@suse.de
+
+- rpm/kernel-binary.spec.in: Fix dependency of kernel-*-devel package (bsc#1184514)
+ The devel package requires the kernel binary package itself for building
+ modules externally.
+- commit 794be7b
After reading this bug I have feeling this is all mixed up. kernel-flavor-devel most certainly does not need kernel-flavor to build external module. If some external module does something stupid in its trigger script, it is this module that needs fixing, not adding workaround that breaks everything.
Anyone cares enough to open bug report?
THESE ARE THE STEPS TO CLEAN UP ALL THOSE UNWANTED “PREEMPTS”:
In Yast, you first UNINSTALL virtualbox-kmp-preempt AND kernel-preempt AND kernel-preempt-devel (with this last one, you choose the third alternative: “keep kernel-syms with broken capacities”)
THEN YOU REBOOT
Then, in Yast again, you put a TABU option (with right mouse) on these three: virtualbox-kmp-preempt AND kernel-preempt AND kernel-preempt-devel ; that way these three won’t bother you anymore, never: they’re “tabu” now.
THEN YOU REBOOT AGAIN
Then, in Yast again, you UPDATE kernel-syms (with this, you choose the third alternative option: “keep kernel-syms with broken capacities”) Don’t bother about those “broken capacities”: they refer to the unwanted preempts.
THEN YOU REBOOT AGAIN
And now your computer works fine, your kernel-default updates will not prompt you anymore to install those ********** “preempts”, and your VirtualBox (or what it was that pulled in those “preempts”) works like a charm.
The first reboot is needed so that you can put the “tabu” option on the three “preempts”;
the second reboot is needed so that the three tabus are fixed and so that you can update your kernel-syms with the right version;
the third reboot is needed to finalize all the steps you’ve taken and to clean up your computer for good.
Have a nice day!