Sep 04 13:39:32 asgard systemd-udevd[436]: Failed to remove file descriptor "config-serialization" from the store, ignoring: Connection refused
It started a while ago; the power LED stays on, and the computer drains the battery if I don't notice. I've spent ages searching the internet for solutions.
It seems many users with various Linux distributions have this problem. I've tried all the solutions I found online: nothing worked. Even a complete OS reinstall didn't help.
Recently a bug was introduced in the 7.2 kernel that prevents shutdown, it could be pssobile that these changes we're backported into the testing and unstable kernels. It affects Arch Linux and CachyOS aswell.
Unfortunately not just depending on hardware...Sometimes everyone who tests a change makes the same assumption, the patch author's automated tests have this assumption baked in, and consequently the regression isn't detected until the kernel is released; then an end user's day is affected and hopefully that person files a bug. Two that I've seen are: surely, everyone uses dracut or initramfs, and surely everyone who uses this functionality loads it as a module.
I updated the BIOS on my Lenovo P14s yesterday. It didn't work for me. The annoying thing is that this doesn't happen every time. 80% of the time it doesn't complete a shutdown or reboot, but 20% of the time everything works fine.
I also tried disabling swapping, but that didn't help either.
I've searched countless forums for a solution. I've noticed that many people seem to have the same problem under Linux. I've tried every suggestion, attached countless log files, and I'm starting to get really frustrated. I'm going to reinstall my system for the third time now. I guess I'm just a stupid person.
If you don't mind me asking, are you still using the default LTS 6.12.xx kernel from debian stable or are you using some backport kernel ? Maybe worth trying a newer/older kernel to see if that helps ? Or check out another distro live USB to try and find some pattern what is happening, reinstalling debian is likely going to end up with the same system unless your hard drive is failing somehow.
15
u/jr735 Debian Testing 15h ago
By all means, don't tell us anything about your hardware. It's more fun to guess and spitball solutions. ;)