WARNING:System won't boot after last du, systemd: segfault error in libc-2.27.so

Started by vayu, 2018/03/08, 07:40:32

Previous topic - Next topic

seasons

I chrooted in and upgraded the kernel. The system now boots. Do I still need to upgrade systemd to 238-1.1 or should I wait for the "official" Debian upgrade?

And a big thank you to those who helped make this a relatively quick/painless fix for a critical bug.

graviton

Thank you @ all, my system is running again after I had made an update before the warnings on Wednesday. That's why I'm a very satisfied siduction user!

Servus graviton


tommy2

@seasons, I waited for the all clear to be announced here and then D-U'd all is well on my end. To upgrade or not to upgrade is for you to decide, however as far as I can tell everything seems to be working without problems.  ;)

tom

drb

@seasons, systemd 238-2 now available and I've dued a 'clean' system with no problems.

samoht



# apt changelog systemd
systemd (238-2) unstable; urgency=medium

  [ Alf Gaida ]
  * core: do not free stack-allocated strings.
    Fixes a crash in systemd when the cpuacct cgroup controller is not
    available. (Closes: #892360)

-- Michael Biebl <biebl@debian.org>  Sat, 10 Mar 2018 01:12:47 +0100

...



Congratulations, @melmarker  :) .

dibl

System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.