http://bugzilla.opensuse.org/show_bug.cgi?id=1184856 Bug ID: 1184856 Summary: After installing 15.2 Update-Test patch 16089, a _second_ reboot is necessary to clear the "zypper ps" entry for systemd-udevd (needing several kernel modules) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance@opensuse.org Reporter: antoine.mechelynck@gmail.com QA Contact: qa-bugs@suse.de Found By: Community User Blocker: --- 15.2 Update-Test patch 16089 is a kernel update so it requires reboot. As I was ready to go to bed (yesterday evening), I shut the computer down instead after installing this patch. On bootup today, I happened to run "zypper ps" from tty2 as soon as the GUI login prompt had come up on tty7. (I had booted kernel-debug because it much reduces the incidence of sporadic one-second X11 extinctions, which are a different bug.) To my surprise, the "zypper ps" output said that the process systemd-udevd required four "now deleted libraries", all of them kernel modules (whose exact names I forgot to write down). I had a look at the log of the latest "zypper patch" log after which I had run "zypper ps", also with logging, and _that_ run of zypper ps had mentioned a need to reboot but no particular process using deleted libraries. Not knowing what to do, and still without logging into X, I typed "init 6" at the tty2 shell prompt in order to reboot. At the end of reboot I logged in on tty2 again and again ran "zypper ps". This time it mentioned "No processes using deleted files found". One possible explanation (but I can't be sure of it) is that I might have logged in too soon, before the "Purge old kernels" bootup job had finished running. But in any case I thought that you might want to look into it: a bug not reported will never be fixed. I supposed that *if* I saw this becaused I logged in too soon this bug can be RESOLVED WONTFIX, but not otherwise. Oh, and in case it might make any difference: I'm running this on a rather new computer with six twincore processors (for a total of 12), running at approximately 3 GHz according to /proc/cpuinfo (but their "model name" is "Intel(R) Core(TM) i5-10500T CPU @ 2.30GHz"), and 32 GiB installed memory. -- You are receiving this mail because: You are on the CC list for the bug.