Package: e2fsprogs Version: 1.44.5-1 Followup-For: Bug #932855 I know it will sound like a support question, but please help me. I have 2 pcs, one with debian unstable i386 and one with debian testing amd64. Obviously, the first one was hit by that bug earlier today.
Because I have no optical drive on my systems so as to load a live cd, I removed the drive with the i386 installation, installed it on the amd64 one and chrooted from there. As suggested here, I installed logsave, exited the chroot and put the drive back in place. However, the problem still persists. Any ideas why? -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages e2fsprogs depends on: ii libblkid1 2.33.1-0.1 ii libc6 2.28-10 ii libcom-err2 1.44.5-1 ii libext2fs2 1.44.5-1 ii libss2 1.44.5-1 ii libuuid1 2.33.1-0.1 Versions of packages e2fsprogs recommends: pn e2fsprogs-l10n <none> Versions of packages e2fsprogs suggests: pn e2fsck-static <none> pn fuse2fs <none> pn gpart <none> ii parted 3.2-25+b1 -- no debconf information
