https://bugzilla.suse.com/show_bug.cgi?id=1233416 https://bugzilla.suse.com/show_bug.cgi?id=1233416#c1 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Printing |Kernel Flags| |needinfo?(austinov@yandex.r | |u) QA Contact|jsmeix@suse.com |qa-bugs@suse.de CC| |austinov@yandex.ru, | |jsmeix@suse.com Assignee|jsmeix@suse.com |kernel-bugs@opensuse.org --- Comment #1 from Johannes Meixner <jsmeix@suse.com> --- I reassign this issue from "Printing" to "Kernel" so kernel people could have a look here because I cannot debug kernel related issues (I know nothing about kernel internals). I assume that the root cause of this kernel panic is not in the CUPS software. I think if there was a bug in the CUPS software that causes a kernel panic, we would have got many such issue reports but (at least for now) this is the only one. The last code change in the openSUSE CUPS RPMs is from Mon Sep 30 2024 (RPM changelog entry date), the CUPS "Version upgrade to 2.4.11" which was submitted to openSUSE:Factory on 2024-10-01, see https://build.opensuse.org/request/show/1204788 My blind guess of the root cause of this kernel panic is some specific hardware, in particular pluggable hardware, like USB devices and things like that. Alex Ustinov, I would try out if the kernel panic goes away when you unplug as many hardware as possible (e.g. all external hardware from your laptop) and retry "lpinfo -v". When "lpinfo -v" runs it calls each CUPS backend in /usr/lib/cups/backend/ to let each CUPS backend report the printing devices which are autodetected by each CUPS backend. So you may try out if it helps to move away CUPS backends from /usr/lib/cups/backend/ to find out if a particular CUPS backend triggers this kernel panic which may indicate where the actual root cause is. But first and foremost you should do some basic system integrity checks: Verify that the dependencies of all installed packages are satisfied as 'root' via # zypper verify --dry-run which results for example on my system -------------------------------------------------------- # zypper verify --dry-run Loading repository data... Reading installed packages... Dependencies of all installed packages are satisfied. -------------------------------------------------------- or as needed with more detailed output via # zypper verify --dry-run --details Also verify that your installed RPM files are OK, in particular your installed "cups" related things as 'root' via # rpm -V $( rpm -qa | grep cups ) or even verify all your installed RPM files via # rpm -Va (may result a long list - perhaps too long to be useful). -- You are receiving this mail because: You are the assignee for the bug.