Hi, On 2021-08-28 11:17, Martin-Éric Racine wrote: > Package: libc6 > Version: 2.31-17 > Severity: grave > Justification: renders package unusable > > Since 2.31-17 trickled into Bookworm, a number of executables (including APT and GDB) die with sig ILL. An example: Have you upgraded other packages at the same time? At a first glance it doesn't seem related to libc6. > $ sudo coredumpctl debug 1011 > PID: 1011 (apt-get) > UID: 0 (root) > GID: 0 (root) > Signal: 4 (ILL) > Timestamp: Sat 2021-08-28 11:00:34 EEST (3min 22s ago) > Command Line: apt-get --quiet --quiet update > Executable: /usr/bin/apt-get > Control Group: /user.slice/user-1000.slice/session-4.scope > Unit: session-4.scope > Slice: user-1000.slice > Session: 4 > Owner UID: 1000 (perkelix) > Boot ID: 77dfa6eb16584c02b84de4e2b8feb781 > Machine ID: 1063a9d1fb9df6e371ea9f94491345ed > Hostname: geode > Storage: /var/lib/systemd/coredump/core.apt-get.0.77dfa6eb16584c02b84de4e2b8feb781.1011.1630137634000000.zst > Message: Process 1011 (apt-get) of user 0 dumped core. > > Stack trace of thread 1011: > #0 0x00000000b7ad2ed0 __cpu_indicator_init (libgcc_s.so.1 + 0x2ed0) > #1 0x00000000b7faf02c call_init (ld-linux.so.2 + 0x1102c) > #2 0x00000000b7faf132 call_init (ld-linux.so.2 + 0x11132) > #3 0x00000000b7f9f0fa _dl_start_user (ld-linux.so.2 + 0x10fa) The SIGILL happens in __cpu_indicator_init which is provided by libgcc-s1. Bookworm got a new upstream version of this package compared to bullseye, so if you also upgraded it, it's more likely to be the issue. In that case, have you tried to downgrade it? Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
Attachment:
signature.asc
Description: PGP signature