Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  WARNING:System won't boot after last du, systemd: segfault error in libc-2.27.so  (Read 8578 times)

Offline seasons

  • User
  • Posts: 269
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.

Offline graviton

  • User
  • Posts: 62
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


Offline tommy2

  • User
  • Posts: 128
@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

Offline drb

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

Offline samoht

  • User
  • Posts: 478

Code: [Select]
# 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  :) .

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.345
    • Land of the Buckeye

Quote from: samoht
Congratulations, @melmarker

+1
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO