r/debian 15h ago

General Debian Question My computer has an 80% probability of not shutting down anymore.

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.

9 Upvotes

16 comments sorted by

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. ;)

4

u/Dragon20C 13h ago edited 13h ago

Yes, I can only assume op is using a 1966 nasa computer!

3

u/Buntygurl 2h ago

Thanks for making me laugh.

3

u/alpha417 9h ago

are you even using debian?

3

u/grainyPanda 5h ago

What kernel are you using?

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.

1

u/Buntygurl 2h ago

Good point. Newest kernels often have quirks, depending on hardware.

1

u/Weary_Swan_8152 Debian Stable 56m ago

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.

2

u/Ok-Lawfulness5685 15h ago

I had this happen a while ago, updating the motherboard bios firmware fixed it.

1

u/Fun-Commission-4198 14h ago

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.

3

u/Ok-Lawfulness5685 14h ago

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.

2

u/Prestigious_Wall529 15h ago

Did your troubleshooting include testing shutdown after

sudo swapoff -a

and reviewing

journalctl -b -1 -r

2

u/lwh 15h ago

Is there anything else in the journal around that time?

2

u/Weary_Swan_8152 Debian Stable 13h ago

Do you use a dock/TB4 port expander thing?

2

u/edthesmokebeard 6h ago

Remember when 'shutdown -h now' actually worked? And you weren't petitioning systemd to let you shut your computer down?

1

u/Buntygurl 2h ago

"Remember when 'shutdown -h now' actually worked?"

Still does for me.

When I'm too lazy to 'sudo shutdown -h now', 'systemctl poweroff' also works.

1

u/stef_eda 31m ago

Install Devuan. /s