You are not logged in.

#1 2018-08-14 13:12:19

rogerthat
Member
Registered: 2018-08-14
Posts: 48

Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

Hello. I ran a system upgrade ("pacman -Syyu") today August 14. The last time I ran an upgrade was August 4.
I got several messages during the upgrade process about:

/usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by **varies**)

Running "pacman -Qs glibc" shows that glibc 2.27-32 (base) is the latest available version.
I'm not sure how to fix this.

Below is the full upgrade log...

-----------

[2018-08-14 12:42] [PACMAN] Running 'pacman -Syyu'
[2018-08-14 12:42] [PACMAN] synchronizing package lists
[2018-08-14 12:42] [PACMAN] starting full system upgrade
[2018-08-14 12:45] [ALPM] transaction started
[2018-08-14 12:45] [ALPM] upgraded archlinux-keyring (20180627-1.0 -> 20180808-1.0)
[2018-08-14 12:45] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2018-08-14 12:45] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2018-08-14 12:45] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2018-08-14 12:45] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key FB871F0131FEA4FB5A9192B4C8880A6406361833...
[2018-08-14 12:45] [ALPM-SCRIPTLET]   -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 40776A5221EF5AD468A4906D42A1DB15EC133BAD...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key DBE7D3DD8C81D58D0A13D0E76BC26A17B9B7018A...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
[2018-08-14 12:46] [ALPM-SCRIPTLET]   -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
[2018-08-14 12:46] [ALPM-SCRIPTLET] ==> Updating trust database...
[2018-08-14 12:46] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2018-10-19
[2018-08-14 12:46] [ALPM] upgraded readline (7.0.003-1 -> 7.0.005-1.0)
[2018-08-14 12:46] [ALPM] upgraded bash (4.4.019-1.0 -> 4.4.023-1.0)
[2018-08-14 12:46] [ALPM] upgraded binutils (2.30-3.0 -> 2.31.1-3.0)
[2018-08-14 12:46] [ALPM] upgraded harfbuzz (1.8.4-1.0 -> 1.8.5-1.0)
[2018-08-14 12:46] [ALPM] upgraded fribidi (1.0.4-1.0 -> 1.0.5-1.0)
[2018-08-14 12:46] [ALPM] upgraded device-mapper (2.02.180-1.0 -> 2.02.181-1.0)
[2018-08-14 12:46] [ALPM] upgraded cryptsetup (2.0.3-2.1 -> 2.0.4-1.0)
[2018-08-14 12:46] [ALPM] upgraded libpcap (1.8.1-2 -> 1.9.0-1.0)
[2018-08-14 12:46] [ALPM] upgraded gdbm (1.16-1.0 -> 1.17-1.0)
[2018-08-14 12:46] [ALPM] upgraded libunistring (0.9.9-1.0 -> 0.9.10-1.0)
[2018-08-14 12:46] [ALPM] upgraded mesa (18.1.4-1.0 -> 18.1.5-1.0)
[2018-08-14 12:46] [ALPM] upgraded colord (1.4.3-1.0 -> 1.4.3-2.0)
[2018-08-14 12:46] [ALPM] upgraded pango (1.42.1-1.0 -> 1.42.3-1.0)
[2018-08-14 12:46] [ALPM] upgraded wayland-protocols (1.14-1.0 -> 1.15-1.0)
[2018-08-14 12:46] [ALPM] upgraded chromium (68.0.3440.75-1.0 -> 68.0.3440.84-1.0)
[2018-08-14 12:46] [ALPM] upgraded libatomic_ops (7.6.4-1.0 -> 7.6.6-1.0)
[2018-08-14 12:46] [ALPM] upgraded mkinitcpio-busybox (1.28.3-1.0 -> 1.29.2-1.0)
[2018-08-14 12:46] [ALPM] upgraded linux (4.17.3-1.0 -> 4.17.11-1.0)
[2018-08-14 12:46] [ALPM] upgraded lvm2 (2.02.180-1.0 -> 2.02.181-1.0)
[2018-08-14 12:46] [ALPM] upgraded pkgconf (1.5.2-1.1 -> 1.5.3-1.0)
[2018-08-14 12:46] [ALPM] upgraded procps-ng (3.3.14-1.0 -> 3.3.15-1.0)
[2018-08-14 12:46] [ALPM] transaction completed
[2018-08-14 12:46] [ALPM] running '60-linux.hook'...
[2018-08-14 12:47] [ALPM] running '90-linux-lts.hook'...
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Starting build: 4.14.56-1.0-lts
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-08-14 12:47] [ALPM-SCRIPTLET] /usr/lib/initcpio/busybox: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/initcpio/busybox)
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Starting build: 4.14.56-1.0-lts
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-08-14 12:47] [ALPM-SCRIPTLET] /usr/lib/initcpio/busybox: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/initcpio/busybox)
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-08-14 12:47] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-08-14 12:47] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-08-14 12:48] [ALPM] running '90-linux.hook'...
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Starting build: 4.17.11-arch1
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-08-14 12:48] [ALPM-SCRIPTLET] /usr/lib/initcpio/busybox: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/initcpio/busybox)
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Starting build: 4.17.11-arch1
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-08-14 12:48] [ALPM-SCRIPTLET] /usr/lib/initcpio/busybox: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/initcpio/busybox)
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-08-14 12:48] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-08-14 12:48] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-08-14 12:49] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-08-14 12:49] [ALPM] running 'glib-compile-schemas.hook'...
[2018-08-14 12:49] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-08-14 12:49] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-08-14 12:49] [ALPM-SCRIPTLET] /usr/bin/systemctl: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
[2018-08-14 12:49] [ALPM-SCRIPTLET] /usr/bin/systemctl: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
[2018-08-14 12:49] [ALPM] running 'systemd-sysusers.hook'...
[2018-08-14 12:49] [ALPM-SCRIPTLET] /usr/bin/systemd-sysusers: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
[2018-08-14 12:49] [ALPM-SCRIPTLET] /usr/bin/systemd-sysusers: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
[2018-08-14 12:49] [ALPM] running 'systemd-tmpfiles.hook'...
[2018-08-14 12:49] [ALPM-SCRIPTLET] /usr/bin/systemd-tmpfiles: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
[2018-08-14 12:49] [ALPM-SCRIPTLET] /usr/bin/systemd-tmpfiles: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
[2018-08-14 12:49] [ALPM] running 'systemd-udev-reload.hook'...
[2018-08-14 12:49] [ALPM-SCRIPTLET] /usr/bin/udevadm: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
[2018-08-14 12:49] [ALPM-SCRIPTLET] /usr/bin/udevadm: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
[2018-08-14 12:49] [ALPM] running 'systemd-update.hook'...
[2018-08-14 12:49] [ALPM] running 'texinfo-install.hook'...
[2018-08-14 12:49] [ALPM] running 'update-desktop-database.hook'...

Last edited by rogerthat (2018-08-14 22:19:34)

Offline

#2 2018-08-14 19:32:56

timsong
Member
Registered: 2018-04-03
Posts: 29

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

I'm getting the same GLIB errors with pacman -Syu. Kernel rebuilt with errors and then system would not shutdown or start. Had to use partimage image to rewind my system. I'm using the lts kernel.

I'm running pacman -Syu again now (quite a few updates) and I'll post the results if the errors happen again on kernel build

Last edited by timsong (2018-08-14 19:36:01)

Offline

#3 2018-08-14 19:43:36

timsong
Member
Registered: 2018-04-03
Posts: 29

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

:: Synchronising package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (53) aircrack-ng-1.3-1.0  archlinux-keyring-20180808-1.0  bash-4.4.023-1.0  binutils-2.31.1-3.0  bubblewrap-0.3.0-1.0  colord-1.4.3-2.0  cryptsetup-2.0.4-1.0  device-mapper-2.02.181-1.0  fribidi-1.0.5-1.0  fuse-common-3.2.5-1.0  fuse2-2.9.8-1.0  fuse3-3.2.5-1.0  gdbm-1.17-1.0  geoclue2-2.4.11-1.0  geoip-1.6.12-1.0  gnome-bluetooth-3.28.2-1.0  harfbuzz-1.8.5-1.0  harfbuzz-icu-1.8.5-1.0  haveged-1.9.2-1.0  intel-tbb-2018_20180618-1.0  libatomic_ops-7.6.6-1.0  libgphoto2-2.5.19-1.0  libnm-1.12.2-1.0  libnm-glib-1.12.2-1.0  libpcap-1.9.0-1.0  libpulse-12.2-2.0  libsidplayfp-1.8.8-1.0  libunistring-0.9.10-1.0  lvm2-2.02.181-1.0  mesa-18.1.5-1.0  minizip-1:1.2.11-3.0  mkinitcpio-busybox-1.29.2-1.0  mutter-3.28.3-2.0  networkmanager-1.12.2-1.0  pango-1.42.3-1.0  paprefs-1.0-1.0  pipewire-0.2.2-1.0  pkgconf-1.5.3-1.0  procps-ng-3.3.15-1.0  pulseaudio-12.2-2.0  pulseaudio-bluetooth-12.2-2.0  readline-7.0.005-1.0  serd-0.30.0-1.0  sord-0.16.2-1.0  sratom-0.6.2-1.0  suil-0.10.0-3.0  tracker-2.1.1-1.0  udisks2-2.7.7-1.0  wayland-protocols-1.15-1.0  webrtc-audio-processing-0.3.1-1.0  wine-3.13-1.0  xfwm4-4.12.5-1.0  zlib-1:1.2.11-3.0

Total Installed Size:  621.93 MiB
Net Upgrade Size:        3.23 MiB

checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
upgrading readline...
upgrading bash...
upgrading libpcap...
upgrading gdbm...
upgrading zlib...
upgrading aircrack-ng...
upgrading archlinux-keyring...
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
  -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
  -> Disabling key FB871F0131FEA4FB5A9192B4C8880A6406361833...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
  -> Disabling key 50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 40776A5221EF5AD468A4906D42A1DB15EC133BAD...
  -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
  -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
  -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key DBE7D3DD8C81D58D0A13D0E76BC26A17B9B7018A...
  -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
  -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
  -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
==> Updating trust database...
gpg: next trustdb check due at 2018-10-19
upgrading binutils...
upgrading bubblewrap...
upgrading device-mapper...
upgrading cryptsetup...
upgrading colord...
upgrading fribidi...
upgrading fuse-common...
upgrading fuse2...
upgrading fuse3...
upgrading libunistring...
upgrading geoclue2...
upgrading geoip...
upgrading libpulse...
upgrading webrtc-audio-processing...
upgrading pulseaudio...
upgrading pulseaudio-bluetooth...
upgrading mesa...
upgrading harfbuzz...
upgrading pango...
upgrading wayland-protocols...
upgrading gnome-bluetooth...
upgrading harfbuzz-icu...
upgrading haveged...
upgrading intel-tbb...
upgrading libatomic_ops...
upgrading libgphoto2...
upgrading libnm...
upgrading libnm-glib...
upgrading libsidplayfp...
upgrading lvm2...
upgrading minizip...
upgrading mkinitcpio-busybox...
upgrading pipewire...
upgrading mutter...
upgrading procps-ng...
upgrading networkmanager...
New optional dependencies for networkmanager
    iwd: wpa_supplicant alternative
upgrading paprefs...
upgrading pkgconf...
upgrading serd...
upgrading sord...
upgrading sratom...
upgrading suil...
upgrading tracker...
upgrading udisks2...
upgrading wine...
upgrading xfwm4...
:: Running post-transaction hooks...
( 1/12) Updating linux-lts initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 4.14.56-1.0-lts
  -> Running build hook: [base]
/usr/lib/initcpio/busybox: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/initcpio/busybox)
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 4.14.56-1.0-lts
  -> Running build hook: [base]
/usr/lib/initcpio/busybox: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/initcpio/busybox)
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful
( 2/12) Compiling GSettings XML schema files...
( 3/12) Updating icon theme caches...
( 4/12) Registering binary formats...
/usr/lib/systemd/systemd-binfmt: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
/usr/lib/systemd/systemd-binfmt: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
( 5/12) Reloading system manager configuration...
/usr/bin/systemctl: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
/usr/bin/systemctl: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
( 6/12) Updating udev hardware database...
/usr/bin/systemd-hwdb: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
/usr/bin/systemd-hwdb: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
( 7/12) Creating system user accounts...
/usr/bin/systemd-sysusers: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
/usr/bin/systemd-sysusers: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
( 8/12) Creating temporary files...
/usr/bin/systemd-tmpfiles: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
/usr/bin/systemd-tmpfiles: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
( 9/12) Reloading device manager configuration...
/usr/bin/udevadm: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libdevmapper.so.1.02)
/usr/bin/udevadm: /usr/lib/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/libpcap.so.1)
(10/12) Arming ConditionNeedsUpdate...
(11/12) Updating the info directory file...
(12/12) Updating the desktop file MIME type cache...

error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly
error: command failed to execute correctly

Last edited by timsong (2018-08-15 09:54:15)

Offline

#4 2018-08-14 19:46:18

rogerthat
Member
Registered: 2018-08-14
Posts: 48

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

Ahh, yes I am using LTS kernel also!

I rolled back by running pacman -U using the old package versions from my local package cache.
Waiting for a resolution to this issue before trying again.

Last edited by rogerthat (2018-08-14 20:43:32)

Offline

#5 2018-08-14 20:02:04

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 326

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

glibc 2.28 seems to be available in the testing repo, I note, but that's a couple of layers extracted for those of you on an LTS kernel I guess.

You can roll back individual packages using pacman -U /var/cache/pacman/pkg/<old package>, but I'm afraid I've never had to undo a whole -Syu, so I'm not sure how to do that*.  You can also blacklist it to stop it ever being updated again, but hopefully sooner rather than later glibc will make it's way to the release repos anyway.

* Maybe some combination of find with -exec and -newer will help.  But that's all the help I can give at this time.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#6 2018-08-14 22:10:27

bulletmark
Member
Registered: 2018-05-30
Posts: 16

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

This is a problem for everybody, not just those using the LTS kernel. Many system commands (like reboot etc) are failing with that GLIBC_2.28 error. This is a shocking bug.

Offline

#7 2018-08-14 22:17:31

rogerthat
Member
Registered: 2018-08-14
Posts: 48

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

Is there a link to the discussion on the topic?

Offline

#8 2018-08-15 02:08:55

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 326

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

bulletmark wrote:

This is a problem for everybody, not just those using the LTS kernel. Many system commands (like reboot etc) are failing with that GLIBC_2.28 error. This is a shocking bug.

It's unfortunate for sure, but this is a small community project ever since Archlinux mainline dropped i686 support as being uneconomic.  We're all testing the distribution at this stage, although this shows they could perhaps do with a test setup that actually tests the coherence of the non-test repos.

But you can always temporarily add the testing repo, do a pacman -S glibc, then switch it back.  I've been running the x64 version of glibc 2.28 on my 64-bit machine for about a week (I have a perl issue stopping me updating my 32-bit machine at present, although I did just update it to glibc2.28 to test that it was at least possible), so it should be reasonably safe to use, and probably preferable to a machine you can't even shutdown in any case.

To enable the testing repo, open your /etc/pacman.conf in your favourite text editor (you'll need root privs to edit it) and uncomment the two testing lines, then do a pacman -S glibc, then revert your pacman.conf.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#9 2018-08-15 02:15:30

bulletmark
Member
Registered: 2018-05-30
Posts: 16

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

levi wrote:

To enable the testing repo, open your /etc/pacman.conf in your favourite text editor (you'll need root privs to edit it) and uncomment the two testing lines, then do a pacman -S glibc, then revert your pacman.conf.

levi, before I posted above I had already enabled the testing repo and installed the newer glibc (only). I also took testing back out of my pacman.conf. However, then I rebooted and my box never came back up. The box is remote and I can not retrieve the box for a few more days. Is it likely to be hosed?

Offline

#10 2018-08-15 02:23:41

rogerthat
Member
Registered: 2018-08-14
Posts: 48

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

I got lucky that I did not reboot after the initial upgrade that changed linux from 4.17.3-1.0 -> 4.17.11-1.0.
That appears to be the upgrade that caused the glibc errors.

So I was able to rollback all the upgraded packages using my local package cache by looking at the pacman.log.
Then I rebooted, and everything was fine.

Offline

#11 2018-08-15 15:56:54

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 326

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

bulletmark wrote:

The box is remote and I can not retrieve the box for a few more days. Is it likely to be hosed?

You're liable to have to boot it up using an archlinux32 iso, chroot it and fix whatever it's complaining about on the local console if that's at all possible.  I don't really understand why your remote interface didn't come back up.  FWIW I'm running glib 2.28 on linux kernel 4.17.9-1.0 and it all seems okay for here, although I am not running any kind of remote connection server on this machine (but I'm currently connected over ssh to my 64 bit machine which is).


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#12 2018-08-15 16:50:44

bulletmark
Member
Registered: 2018-05-30
Posts: 16

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

@levi, have you rebooted?

I have SSH access to another Unix box on the same local LAN and the failed box doesn't even ping.

Offline

#13 2018-08-15 18:23:18

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 326

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

Yes, I installed it yesterday and shut the computer down overnight.  Absolutely no troubles to report here, unfortunately for you.

glibc is noted as being a dependency of a number of packages, and a quick vgrep notes bash, dhcpd, perl and various packages beginning with lib, any of which might be necessary for a system to boot and bring up a working network connection.  Hopefully if you can get eyes on the machine, it might be reporting a failure in one of these, which might be a hint as to what you need to mess with once you've booted a fresh arch32 iso, mounted and chrooted into the drive.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#14 2018-08-17 07:52:21

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 661
Website

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

This is a glibc 2.28 issue and has nothing to do with the linux kernel. Some packages (systemd, udevadm) were published early to stable with a link
dependency to glibc 2.28. But glibc 2.28 is in stable now, so there should be no more problems.

See also https://bbs.archlinux32.org/viewtopic.php?id=2551

What I'm not sure about is: glibc 2.28 dropped some POSIX functions (for instance readdir_r) and removed some private symbols like
__freadahead. This can (and does) cause major issues in some packages (those using gnulib for instance). See also the bugs upstream, for
instance: m4 not building on glibc 2.28. Be aware of that if you compile packages from source or from the AUR.

Also the gcc 8.2 toolchain seems to make use of more modern Intel opcodes in the SSE, SSE2 range thus rendering pacman for instance
unusable on really old CPUs. You'll notice an 'Illegal instruction' when updating such a system. There is not much we can do than to
go forward with the i486 branch of Archlinux32 for really old systems (which is not using any of MMX, SSE. SSE2. 3dnow or other extensions).

Offline

#15 2018-08-17 13:01:58

rogerthat
Member
Registered: 2018-08-14
Posts: 48

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

andreas_baumann wrote:

...rendering pacman for instance unusable on really old CPUs. You'll notice an 'Illegal instruction' when updating such a system. There is not much we can do than to go forward with the i486 branch of Archlinux32 for really old systems (which is not using any of MMX, SSE. SSE2. 3dnow or other extensions).

How "pretty old" would that be? :-) I'm not sure how to check my CPU. It's an MSI U100 netbook (with an Intel Atom N270 1.6GHz from 2008 I think).

Last edited by rogerthat (2018-08-17 13:21:58)

Offline

#16 2018-08-17 13:21:20

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 661
Website

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

"cat /proc/cpuinfo" is your friend. :-)
check what kind of flags are printed there..
If you see 'SSE', you're fine. Some things may require 'SSE2', but usually
nothing in a basic installation.

Which reminds me, maybe we should put a minimal requirements page
somewhere in a prominent place on https://www.archlinux32.org..

Offline

#17 2018-08-17 13:23:37

rogerthat
Member
Registered: 2018-08-14
Posts: 48

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

andreas_baumann wrote:

"cat /proc/cpuinfo" is your friend. :-)
check what kind of flags are printed there..
If you see 'SSE', you're fine. Some things may require 'SSE2', but usually
nothing in a basic installation.

Which reminds me, maybe we should put a minimal requirements page
somewhere in a prominent place on https://www.archlinux32.org..

Thanks! Yeah, I've got up to SSSE3.
So can I re-run system update now?

Offline

#18 2018-08-17 13:59:59

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 661
Website

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

yep. :-)
Actually, can you post the 'model name' of /proc/cpuinfo?
This CPU sounds like a 64-bit one..

Offline

#19 2018-08-17 16:29:28

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 326

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

I also have an Atom N270 in an EeePC here.  I think the N270 was one of the last i686-only CPUs intel produced.  It supports SSE, SSE2 and SSSE3 (whatever that is).


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#20 2018-08-17 16:31:17

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 661
Website

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

Ah. Ok, this is one of the few SSSE3-enabled 32-bit CPUs. Normally SSSE3 means 64-bit. That's why I asked.
So, another trusty Archlinux32 user then.. :-)

Offline

#21 2018-08-18 14:18:11

rogerthat
Member
Registered: 2018-08-14
Posts: 48

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

andreas_baumann wrote:

yep. :-)
Actually, can you post the 'model name' of /proc/cpuinfo?
This CPU sounds like a 64-bit one..

/proc/cpuinfo ...

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N270   @ 1.60GHz
stepping	: 2
microcode	: 0x218
cpu MHz		: 800.028
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm movbe lahf_lm dtherm
bugs		:
bogomips	: 3200.09
clflush size	: 64
cache_alignment	: 64
address sizes	: 32 bits physical, 32 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N270   @ 1.60GHz
stepping	: 2
microcode	: 0x218
cpu MHz		: 800.023
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 1
initial apicid	: 1
fdiv_bug	: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm movbe lahf_lm dtherm
bugs		:
bogomips	: 3200.09
clflush size	: 64
cache_alignment	: 64
address sizes	: 32 bits physical, 32 bits virtual
power management:

Offline

#22 2018-08-18 14:54:58

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 661
Website

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

@rogerthat: thanks for the procinfo. This CPU will do just fine with Archlinux 32. :-)

Offline

#23 2018-08-18 19:08:57

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 326

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

bulletmark wrote:

@levi, have you rebooted?

I have SSH access to another Unix box on the same local LAN and the failed box doesn't even ping.

In case this is relevant, I just did another update today and am now running kernel 4.17.14, but on trying to reboot, the screen went blank and went dark (backlight turned off) but the other lights stayed on.  I had to hold down the power button to turn the machine 'off', but on pressing it again to power back up, the power light came on, but nothing else happened.  Thankfully, after yanking the power and powering up from properly cold, everything's back up and running again.

If you've not had chance to get to the machine yet, it might be as simple as powering down the box fully before bringing it back up.  I noticed nothing odd in the bootup messages.

I'll have to try rebooting again before I shut this machine down for the night to confirm rebooting isn't broken.  I normally do a full shutdown and bring this machine back up in the morning.

Update: I rebooted my 64 bit server while it was running kernel 4.17.14 and that came back fine.  Hopefully my 32 bit netbook will do the same in a bit.

Last edited by levi (2018-08-18 22:22:49)


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#24 2018-08-18 22:07:49

bulletmark
Member
Registered: 2018-05-30
Posts: 16

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

levi wrote:

If you've not had chance to get to the machine yet, it might be as simple as powering down the box fully before bringing it back up.

I spoke to the technician where this machine (an old laptop) is located and he said he powered it down for an hour before booting it up again yet it still does not boot. He claims he can not even get into the BIOS, but that may be a procedural issue etc.

He could send the machine back to me or I may just re-provision an old Raspberry Pi or Beaglebone I have lying around, install Arch ARM running my custom app, and sent that over. I am still interested in what happened though so I may drive over this week and have a look myself.

Offline

#25 2018-08-18 22:45:37

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 326

Re: Ran system upgrade, getting "version `GLIBC_2.28' not found" errors

That sounds suspiciously like what I had.  After trying to bring it back using the soft power, the screen remained blank and unpowered, and only the two power lights came on - there was no apparently BIOS boot I could either leave to boot Arch or get into the BIOS configurator.  However, removing power from the laptop (you'll probably have to remove the battery if you're still using one) for no more than 30 seconds meant the next time I pressed the power button it came back fine.

Last edited by levi (2018-08-18 22:45:56)


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

Board footer

Powered by FluxBB