Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: vayu on 2018/03/08, 07:40:32
-
After doing a du I'm getting the error segfault error 4 in libc-2.27.soFreezing ExecutionWhat can I do?
-
same here, system halted
-
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.
-
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.
-
https://tracker.debian.org/pkg/libc
-
Warning came to late for me...
But chroot is not unknown ;-)
-
Is this what you guys are seeing: https://matrix.archlinux.org/_matrix/media/v1/download/matrix.org/vuBrimPJDrNAeSabjxNWAhTG ?
-
So sieht es aus
-
after chroot what command i have to do?:
apt-get install libc /testing?
Thanks
-
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
-
Thanks Geier0815 !!
-
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
-
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.
-
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
-
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
-
How I did mine
Using a usb stick for chroot
If your using apt-cacher-ng your going to have to install that BEFORE you chroot and enable testing in sources
mkdir /mnt/chroot
mount /dev/sda10 /mnt/chroot/
mount --bind /proc /mnt/chroot/proc && mount --bind /run /mnt/chroot/run && mount --bind /sys /mnt/chroot/sys && mount --bind /dev /mnt/chroot/dev && mount --bind /dev/pts /mnt/chroot/dev/pts
chroot /mnt/chroot /bin/bash
apt update; apt install systemd/testing libnss-systemd/testing libpam-systemd/testing libsystemd-dev/testing libsystemd0/testing
apt install systemd/testing libnss-systemd/testing libpam-systemd/testing libsystemd-dev/testing libsystemd0/testing -s
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '237-4' (Debian:testing [amd64]) for 'systemd'
Selected version '237-4' (Debian:testing [amd64]) for 'libsystemd0' because of 'systemd'
Selected version '237-4' (Debian:testing [amd64]) for 'libnss-systemd'
Selected version '237-4' (Debian:testing [amd64]) for 'libpam-systemd'
Selected version '237-4' (Debian:testing [amd64]) for 'libsystemd-dev'
Selected version '237-4' (Debian:testing [amd64]) for 'libsystemd0'
The following packages were automatically installed and are no longer required:
gstreamer1.0-plugins-base:i386 i965-va-driver:i386 libasound2:i386 libasyncns0:i386 libatomic1:i386 libavahi-common-data:i386 libavahi-common3:i386 libavcodec57:i386 libavutil55:i386 libblkid1:i386 libcairo2:i386 libcap2:i386 libcapi20-3
libcapi20-3:i386 libcdparanoia0:i386 libcom-err2:i386 libcrystalhd3:i386 libdb5.3:i386 libdw1 libexif12:i386 libfdk-aac1:i386 libflac8:i386 libfontconfig1:i386 libfreetype6:i386 libgcrypt20:i386 libgd3:i386 libglib2.0-0:i386
libglu1-mesa:i386 libgmp10:i386 libgnutls30:i386 libgomp1:i386 libgphoto2-6:i386 libgphoto2-port12:i386 libgsm1:i386 libgssapi-krb5-2:i386 libgstreamer-plugins-base1.0-0:i386 libgstreamer1.0-0:i386 libhogweed4:i386 libice6:i386
libicu57:i386 libidn2-0:i386 libieee1284-3:i386 libilbc2:i386 libjack-jackd2-0:i386 libjbig0:i386 libjpeg62-turbo:i386 libk5crypto3:i386 libkeyutils1:i386 libkrb5-3:i386 libkrb5support0:i386 libkvazaar4:i386 liblcms2-2:i386
libldap-2.4-2:i386 libltdl7:i386 liblz4-1:i386 liblzma5:i386 libmfx0:i386 libmount1:i386 libmp3lame0:i386 libmpg123-0:i386 libnettle6:i386 libnuma1:i386 libodbc1 libodbc1:i386 libogg0:i386 libopenal1:i386 libopencore-amrnb0:i386
libopencore-amrwb0:i386 libopenh264-4:i386 libopenjp2-7:i386 libopus0:i386 liborc-0.4-0:i386 libp11-kit0:i386 libpcap0.8:i386 libpcre3:i386 libpixman-1-0:i386 libpng16-16:i386 libsamplerate0:i386 libsane-extras:i386 libsasl2-2:i386
libsasl2-modules:i386 libsasl2-modules-db:i386 libselinux1:i386 libshine3:i386 libsm6:i386 libsnappy1v5:i386 libsndfile1:i386 libsndio6.1:i386 libsoxr0:i386 libspeex1:i386 libssl1.1:i386 libswresample2:i386 libtasn1-6:i386 libtheora0:i386
libtiff5:i386 libunistring2:i386 libusb-1.0-0:i386 libuuid1:i386 libv4l-0:i386 libv4lconvert0:i386 libva-drm2:i386 libva-x11-2:i386 libva2:i386 libvdpau-va-gl1:i386 libvdpau1:i386 libvisual-0.4-0:i386 libvo-amrwbenc0:i386 libvorbis0a:i386
libvorbisenc2:i386 libvpx5:i386 libwebp6:i386 libwebpmux3:i386 libwrap0:i386 libx264-155:i386 libx265-151:i386 libxcb-render0:i386 libxcb-shm0:i386 libxcomposite1:i386 libxcursor1:i386 libxi6:i386 libxml2:i386 libxpm4:i386 libxrandr2:i386
libxrender1:i386 libxslt1.1:i386 libxtst6:i386 libxvidcore4:i386 libzvbi0:i386 mesa-va-drivers:i386 mesa-vdpau-drivers:i386 va-driver-all:i386 vdpau-driver-all:i386 wine-devel-amd64
Use 'sudo apt autoremove' to remove them.
Suggested packages:
systemd-container
The following packages will be REMOVED:
libasound2-plugins:i386 libavahi-client3:i386 libcups2:i386 libdbus-1-3:i386 libpulse0:i386 libsane:i386 libsystemd0:i386 systemd-container systemd-coredump wine-devel wine-devel-i386:i386 winehq-devel winetricks
The following NEW packages will be installed:
libnss-systemd libsystemd-dev
The following packages will be DOWNGRADED:
libpam-systemd libsystemd0 systemd
0 upgraded, 2 newly installed, 3 downgraded, 13 to remove and 35 not upgraded.
Remv winetricks [0.0+20180217-1]
Remv winehq-devel [3.3.0~sid]
Remv wine-devel [3.3.0~sid]
Remv wine-devel-i386:i386 [3.3.0~sid]
Remv libasound2-plugins:i386 [1:1.1.5-dmo1]
Remv libcups2:i386 [2.2.6-5]
Remv libsane:i386 [1.0.25-4.1]
Remv libavahi-client3:i386 [0.7-3.1]
Remv libpulse0:i386 [11.1-4]
Remv libdbus-1-3:i386 [1.12.6-2]
Remv libsystemd0:i386 [238-1]
Remv systemd-container [238-1]
Remv systemd-coredump [238-1]
Inst libpam-systemd [238-1] (237-4 Debian:testing [amd64]) []
Inst systemd [238-1] (237-4 Debian:testing [amd64]) []
Inst libsystemd0 [238-1] (237-4 Debian:testing [amd64])
Conf libsystemd0 (237-4 Debian:testing [amd64])
Inst libnss-systemd (237-4 Debian:testing [amd64])
Inst libsystemd-dev (237-4 Debian:testing [amd64])
Conf libpam-systemd (237-4 Debian:testing [amd64])
Conf systemd (237-4 Debian:testing [amd64])
Conf libnss-systemd (237-4 Debian:testing [amd64])
Conf libsystemd-dev (237-4 Debian:testing [amd64])
root@siduction:/#
-
When in chroot, I noticed a new kernel available, so I figured maybe that'll do it, and yes I'm in. The latest kernel update solves it without downgrading systemd. Thanks Towo.
4.15.7-towo.3-siduction-amd64
-
@ dacorsa: Your solution DID work for me !
However, in order to avoid confusion you might have wanted to provide the following explanations / comments:
- libsystemd:i386 may not be present, as on my system; I simply removed it from the install list
- apt-get install first recommends libnss-mymachines and then removes just that package, along with libnss-systemd
Regards,
Chris
-
systemd/238-1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360)
-
I can confirm vayu's observation and solution. Doing a DU in chroot solves the problem.
I set up my chroot like piper set up his, then, apt update; apt-get dist-upgrade
I choose to do a full-upgrade not just the kernel.
Then umount all mounted in chroot.
fini
Once again, thanks towo.
-
There is a fix for systemd by agaida in our repository.
-
Is that 238-1.1?
I fortunately missed this. Is it now safe to du then reboot?
-
Is that 238-1.1?
I fortunately missed this. Is it now safe to du then reboot?
Yes 238-1.1
Get:1 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 libnss-systemd amd64 238-1.1 [184 kB]
Get:2 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 systemd-sysv amd64 238-1.1 [87.0 kB]
Get:3 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 libpam-systemd amd64 238-1.1 [186 kB]
Get:4 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 libsystemd-dev amd64 238-1.1 [263 kB]
Get:5 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 libsystemd0 amd64 238-1.1 [283 kB]
Get:6 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 libnss-myhostname amd64 238-1.1 [109 kB]
Get:7 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 systemd amd64 238-1.1 [3,033 kB]
Get:8 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 udev amd64 238-1.1 [1,183 kB]
Get:9 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main i386 libudev1 i386 238-1.1 [132 kB]
Get:10 http://10.10.10.3:3142/packages.siduction.org/fixes unstable/main amd64 libudev1 amd64 238-1.1 [129 kB]
-
Thanks!
-
And yes, safe to reboot, it worked here ;)
-
4.15.7-towo.3-siduction-amd64
systemd:
Installiert: 238-1.1
Installationskandidat: 238-1.1
no problems - thx
-
Thanks very much to all of you, your posts were really helpful!
I solved it with the lines dacorsa wrote ( I just had to remove the ":i386" thing, and also had to setup my network card with "dhclient -v enp4s0" just after chroot; then everything worked like a charm )
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
-
Thanks dacorsa and Piper
-
Great support in this forum again! Thumbs up, devil, dacorsa, piper, melmarker/Yu Watanabe!
Greetings,
Tom
-
you're welcome!
;D :D ;)
-
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.
-
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
-
@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
-
@seasons, systemd 238-2 now available and I've dued a 'clean' system with no problems.
-
# 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 :) .
-
Congratulations, @melmarker
+1