https://bugzilla.suse.com/show_bug.cgi?id=1183739 https://bugzilla.suse.com/show_bug.cgi?id=1183739#c3 --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Takashi Iwai from comment #1)

[...] Basically this kind of stuff is handled via the weak-link of KMP if it's a usual KMP.

Actually the issue is not related to weak links at all

But Nvidia is an exception, of course, and it doesn't work like that.

Well, things would actually work if plain RPM would be used for installation, where during an update first the new package is being installed and then the old package is being uninstalled. In that case my %triggerpostun script for kernel-default would not find an errorneously empty /lib/modules/<kernel-version> directory and it would not remove the nvidia kernel modules. Unfortunately YaST/zypper changes the order and removes first the old package and then installs the new package. And then my cleanup approach fails when this kernel update uses the same /lib/modules directories.

That said, from the kernel side, this is likely resolved as FEATURE. If any, Nvidia driver should have a better workaround for this corner case (e.g. listing the modules in ghost).

I don't see how this should help. Anyway, if you really want to keep this as feature then for one reason. You obviously cannot have installed two kernel versions of this kind when they share the same directory and switch between these for booting. I already removed my %triggerpostun script in the updated nvidia packages. A repository update is triggered. -- You are receiving this mail because: You are the assignee for the bug.