seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2020/11/30, 11:56:00


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: WARNING:System won't boot after last du, systemd: segfault error in libc-2.27.so  (Read 4534 times)

0 Members and 1 Guest are viewing this topic.

Offline vayu

  • User
  • Posts: 222
After doing a du I'm getting the error segfault error 4 in libc-2.27.soFreezing ExecutionWhat can I do?
« Last Edit: 2018/03/08, 08:21:41 by devil »

Offline dacorsa

  • User
  • Posts: 68
same here, system halted

Offline GoinEasy9

  • User
  • Posts: 473
Both my new KDE install and my older lxqt install ... same error.


Edit: From Debian Bugzilla:
Debian Bug report logs: Bugs in package libc-2.27.so in unstable There is no maintainer for libc-2.27.so. This means that this package no longer exists (or never existed). Please do not report new bugs against this package.
« Last Edit: 2018/03/08, 07:58:24 by GoinEasy9 »
Linux Counter number 348347

Online devil

  • Administrator
  • User
  • *****
  • Posts: 4.452
This one is not nice. Seems to be systemd!  https://bbs.archlinux.org/viewtopic.php?id=235126


The thread on the arch forum says, chrooting in and downgrading systemd aynd all related packages is the only way out, if you have the segfault error at boot.

Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.787
  • we are the priests ... of the temples of syrinx
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline Geier0815

  • User
  • Posts: 496
Warning came to late for me...
But chroot is not unknown ;-)
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Online devil

  • Administrator
  • User
  • *****
  • Posts: 4.452

Offline Geier0815

  • User
  • Posts: 496
So sieht es aus
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Offline dacorsa

  • User
  • Posts: 68
after chroot what command i have to do?:


apt-get install libc /testing?


Thanks

Offline Geier0815

  • User
  • Posts: 496
It was not logged in my chroot, but it were 4 or 5 packages I had to downgrade. "apt install systemd/testing libnss-systemd/testing libpam-systemd/testing libsystemd-dev/testing" something like that. You have to look what packages the apt install wants to remove
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Offline dacorsa

  • User
  • Posts: 68
Thanks Geier0815 !!

Offline Ninefix

  • User
  • Posts: 6
    • Informatico e sistemista
Hi all, I can confirm that the system doesn't boot after last dist-upgrade, but if you use a 4.10.x kernel it'll boot normally.


But remember: 4.10.x isn't patched against Meltdown and Spectre


Bye

Offline clubex

  • User
  • Posts: 265
This hit me rather hard during my lunchtime du. The worst bit for me (which I still haven't resolved) is losing /dns so I can't even downgrade any packages in the normal way. I know this is sid but nothing should break a system this badly.

Offline dacorsa

  • User
  • Posts: 68
ohhh sorry i have made chroot but i don't have network... so i can't download packages... why with chroot i don't have connection?


Thanks

Offline dacorsa

  • User
  • Posts: 68
SOLVED  :) :



mkdir /mnt/sid
fdisk -l
mount /dev/sda1 /mnt/sid
mv /mnt/sid/etc/resolv.conf /mnt/sid/etc/resolv.conf2
cp /etc/resolv.conf  /mnt/sid/etc/resolv.conf
mount --bind /dev /mnt/sid/dev
mount --bind /proc /mnt/sid/proc
mount --bind /sys /mnt/sid/sys
chroot /mnt/sid /bin/bash
apt-get install systemd=237-2.1 libsystemd0=237-2.1 libpam-systemd=237-2.1 libsystemd0:i386=237-2.1 systemd-container=237-2.1 systemd-coredump=237-2.1