[Unstable Update] 2021-12-13 - Python 3.10 Rebuilds

I have updated shellcheck but it’s complaining about the wrong GLIBC version: 2.34

(Installed is 2.33)

This is a known problem: FS#73726 : shellcheck 0.8.0-25 is built against too new glibc

I hope that this doesn’t affect important programs.

@mithrial Some packages were accidentally rebuilt against the new toolchain. Short term solution - downgrade. Bug report:


Was python-pyqt5 downgraded from 5.15.6-7.1 to 5.15.6-7 on purpose?
I’ve tried refreshing the mirrors couple of times, since sometimes pacman-mirrors could choose outdated mirrors for me.


Yes, it was. We dropped our overlay that is no longer necessary and was causing issues.


Is it just me or does today’s plymouth update break gdm-plymouth? :thinking:

Upgraded the packages below:

[2022-02-12T14:48:56-0600] [ALPM] upgraded archlinux-appstream-data (20220107-1 -> 20220211-1)
[2022-02-12T14:48:56-0600] [ALPM] upgraded opus (1.3.1-2 -> 1.3.1-3)
[2022-02-12T14:48:56-0600] [ALPM] upgraded gtk-update-icon-cache (1:4.6.0-3 -> 1:4.6.1-1)
[2022-02-12T14:48:56-0600] [ALPM] upgraded gtk3 (1:3.24.31-1 -> 1:3.24.31-2)
[2022-02-12T14:48:57-0600] [ALPM] upgraded evolution-data-server (3.42.3-1 -> 3.42.4-2)
[2022-02-12T14:48:57-0600] [ALPM] upgraded libarchive (3.5.3-2 -> 3.6.0-1)
[2022-02-12T14:48:57-0600] [ALPM] upgraded evolution (3.42.3-1 -> 3.42.4-1)
[2022-02-12T14:48:57-0600] [ALPM] upgraded libmm-glib (1.18.4-1 -> 1.18.6-1)
[2022-02-12T14:48:57-0600] [ALPM] upgraded gtk4 (1:4.6.0-3 -> 1:4.6.1-1)
[2022-02-12T14:48:57-0600] [ALPM] upgraded flatpak (1.12.4-1 -> 1.12.5-1)
[2022-02-12T14:48:58-0600] [ALPM] upgraded plymouth (0.9.5.r84.ge554475-1 -> 22.02.122-4)
[2022-02-12T14:48:58-0600] [ALPM] upgraded libgdm-plymouth (41.0+r15+g23ebe617-1 -> 41.3-4)
[2022-02-12T14:48:58-0600] [ALPM] upgraded gjs (2:1.70.1-1 -> 2:1.70.1-2)
[2022-02-12T14:48:58-0600] [ALPM] upgraded libwacom (2.0.0-2 -> 2.1.0-1)
[2022-02-12T14:48:58-0600] [ALPM] upgraded gdm-plymouth (41.3-2 -> 41.3-4)
[2022-02-12T14:48:58-0600] [ALPM] upgraded gnome-maps (41.2-1 -> 41.4-1)
[2022-02-12T14:48:58-0600] [ALPM] upgraded gnome-shell-extension-arcmenu (21-1 -> 22-1)
[2022-02-12T14:48:58-0600] [ALPM] upgraded gnome-software (41.3-1 -> 41.4-1)
[2022-02-12T14:48:58-0600] [ALPM] upgraded libadwaita (1:1.0.1-1 -> 1:1.0.2-1)
[2022-02-12T14:48:58-0600] [ALPM] upgraded libsigc++ (2.10.7-2 -> 2.10.8-1)
[2022-02-12T14:48:58-0600] [ALPM] warning: directory permissions differ on /boot/
[2022-02-12T14:48:59-0600] [ALPM] upgraded linux510 (5.10.99-1 -> 5.10.100-1)
[2022-02-12T14:48:59-0600] [ALPM] warning: directory permissions differ on /boot/
[2022-02-12T14:49:00-0600] [ALPM] upgraded linux515 (5.15.22-1 -> 5.15.23-1)
[2022-02-12T14:49:00-0600] [ALPM] upgraded manjaro-gnome-extension-settings (20211226-2 -> 20220211-1)
[2022-02-12T14:49:00-0600] [ALPM] upgraded polari (41.0-1 -> 41.0+r11+g0f0a4b54-1)
[2022-02-12T14:49:00-0600] [ALPM] upgraded python-setuptools (1:59.1.1-1 -> 1:59.2.0-1)
[2022-02-12T14:49:00-0600] [ALPM] upgraded python-prompt_toolkit (3.0.27-1 -> 3.0.28-1)
[2022-02-12T14:49:00-0600] [ALPM] upgraded qt5-base (5.15.2+kde+r297-1.1 -> 5.15.2+kde+r297-2)
[2022-02-12T14:49:00-0600] [ALPM] upgraded spice-gtk (0.39-3 -> 0.39-4)
[2022-02-12T14:49:00-0600] [ALPM] upgraded squashfs-tools (4.5-1 -> 4.5-2)

Then, I rebooted my system. Instead of getting the usual GDM’s login screen, I got the infamous “Something has gone wrong …blah blah … Contact a System Administrator:laughing:

Went to the journal to confirm:

Feb 12 16:09:01 manjaro-unstable gdm[448]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.11 was not provided by any .service files
Feb 12 16:09:01 manjaro-unstable login[1642]: pam_systemd(login:session): Failed to release session: Interrupted system call

So yeah, there’s no doubt that GDM broke for me with this update.

I haven’t checked yet about this issue upstream, but for now, I was able to get it back working by reverting anything gdm-plymouth related:

[2022-02-12T16:05:13-0600] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/gdm-plymouth-41.3-2-x86_64.pkg.tar.zst'
... [truncated]
[2022-02-12T16:06:55-0600] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/libgdm-plymouth-41.0+r15+g23ebe617-1-x86_64.pkg.tar.zst'
... [truncated]
[2022-02-12T16:08:27-0600] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/plymouth-0.9.5.r84.ge554475-1-x86_64.pkg.tar.zst'
... [truncated]

Any thoughts? :slightly_smiling_face:

It’s not just you, it happened to me as well on my secondary laptop with an AMD APU using GNOME Wayland. I held off updating plymouth for awhile as I couldn’t figure out why it was happening. No one has posted any complaints for the gdm-plymouth & plymouth AUR packages, so I figured I’d push the plymouth update while I was updating gdm-plymouth.

Whatever is causing it, I’d prefer not to keep downgraded packages. Let’s see if it affects anyone else and and figure out what’s causing it.

EDIT: Just to be sure, make sure you’re using gdm.service, not gdm-plymouth.service:

systemctl disable --now gdm-plymouth
systemctl enable --now gdm

This can be done from a TTY if necessary.

1 Like

Seems others are affected too. Please revert and stick to the working version.

1 Like

Hey @Yochanan

Sure thing :slightly_smiling_face:

systemctl | grep gdm                                                                                                                    ✔ 
  gdm.service                                                                                           loaded active running   GNOME Display Manager

I spent some time today playing around with packages. So far this is the last known combination that works for me without breakage:

sudo pacman -Qi gdm-plymouth libgdm-plymouth plymouth | grep -e 'Name\|Version'
Name            : gdm-plymouth
Version         : 41.3-2
Name            : libgdm-plymouth
Version         : 41.3-2
Name            : plymouth
Version         : 22.02.122-4

The only thing though is that I built libgdm-plymouth from the AUR .

It looks like the latest “stable” version for both gdm-plymouth and libgdm-plymouth available in the AUR is 41.3-2.

I took a look at the repo log on GitLab. Perhaps the problem is line 17 in the commit below? :thinking:

Yep, i am also having the same problem with the latest unstable updates.

so this might be connected …

1 Like

I do not know what exact target dependency it was and now is updated but I see that the [Testing Update] 2021-12-07 - Mesa 21.3.1, Breath 21.2, Gnome 41.2 - #10 by alven bug reported earlier now is gone (at last!) in the current state of unstable branch.

last updates I got
~/Desktop ❯ tail -n200 /var/log/pacman.log | grep -E 'upgraded'
[2022-02-12T11:19:40+0300] [ALPM] upgraded archlinux-appstream-data (20220107-1 -> 20220211-1)
[2022-02-12T11:19:42+0300] [ALPM] upgraded gtk-update-icon-cache (1:4.6.0-3 -> 1:4.6.1-1)
[2022-02-12T11:20:01+0300] [ALPM] upgraded gtk3 (1:3.24.31-1 -> 1:3.24.31-2)
[2022-02-12T11:20:44+0300] [ALPM] upgraded opus (1.3.1-2 -> 1.3.1-3)
[2022-02-12T11:20:47+0300] [ALPM] upgraded kactivitymanagerd (5.23.5-1.1 -> 5.24.0-1)
[2022-02-12T11:20:47+0300] [ALPM] upgraded lib32-opus (1.3.1-1 -> 1.3.1-2)
[2022-02-12T11:20:50+0300] [ALPM] upgraded libmm-glib (1.18.4-1 -> 1.18.6-1)
[2022-02-12T11:20:51+0300] [ALPM] upgraded libqmi (1.30.2-1 -> 1.30.4-1)
[2022-02-12T11:20:53+0300] [ALPM] upgraded libsigc++ (2.10.7-2 -> 2.10.8-1)
[2022-02-12T11:20:54+0300] [ALPM] upgraded modemmanager (1.18.4-1 -> 1.18.6-1)
[2022-02-12T11:21:01+0300] [ALPM] upgraded squashfs-tools (4.5-1 -> 4.5-2)
[2022-02-13T17:45:26+0300] [ALPM] upgraded glib2 (2.70.3-1 -> 2.70.4-1)
[2022-02-13T17:47:04+0300] [ALPM] upgraded go (2:1.17.6-2 -> 2:1.17.7-1)
[2022-02-13T17:47:14+0300] [ALPM] upgraded gpgme (1.17.0-1 -> 1.17.0-2)
[2022-02-13T17:47:34+0300] [ALPM] upgraded harfbuzz (3.3.2-1 -> 3.4.0-1)
[2022-02-13T17:47:34+0300] [ALPM] upgraded gtk-update-icon-cache (1:4.6.1-1 -> 1:4.6.1-2)
[2022-02-13T17:47:55+0300] [ALPM] upgraded gtk3 (1:3.24.31-2 -> 1:3.24.31-3)
[2022-02-13T17:47:59+0300] [ALPM] upgraded harfbuzz-icu (3.3.2-1 -> 3.4.0-1)
[2022-02-13T17:48:53+0300] [ALPM] upgraded imagemagick ( ->
[2022-02-13T17:49:00+0300] [ALPM] upgraded libspectre (0.2.9-2 -> 0.2.10-1)
[2022-02-13T17:49:06+0300] [ALPM] upgraded libwacom (2.0.0-2 -> 2.1.0-1)
[2022-02-13T17:49:20+0300] [ALPM] upgraded lirc (1:0.10.1-10 -> 1:0.10.1-11)
[2022-02-13T17:49:48+0300] [ALPM] upgraded python-setuptools (1:59.1.1-1 -> 1:59.2.0-1)
[2022-02-13T17:49:52+0300] [ALPM] upgraded signon-ui (0.17+20171022-2 -> 0.17+20171022-3)
[2022-02-13T17:49:53+0300] [ALPM] upgraded xdg-dbus-proxy (0.1.2-3 -> 0.1.3-1)
[2022-02-13T17:50:05+0300] [ALPM] upgraded zsh (5.8-1 -> 5.8.1-1)
[2022-02-13T17:55:46+0300] [ALPM] upgraded opensnitch-git (1.5.0.r1.feaf8de-1 -> 1.5.0.r2.dd7cb13-1)
~/Desktop ❯ 

@El_Brujo @hritwik It’s fixed with gdm-plymouth / libgdm-plymouth 41.3-5.

Thanks for the update on situation ! :+1:

Yep, I confirm the issue is resolved with these packages. :+1:

Now I see where the issue was :slightly_smiling_face:


EDIT: Kernel rebuilds are done.

PSA: The NVIDIA 510.54 drivers are pushed along with extramodules ONLY for kernels 5.10, 5.15, 5.16 & 5.17.

Those who are using 5.4, 4.19, 4.9, or any RT kernel will need to remove the old linuxXXX-nvidia 510.47.03 package, install nvidia-dkms and run mkinitcpio -P.

Reason being GCC 11.2.0 is out and the kernels were built with 11.1.0. With the next batch of kernel updates, extramodules will be built as per usual.


Dkms seems to be broken today and will not make nvidia-dkms.

1 Like

Please wait. Rebuilds are on the way soon.

1 Like

Thank You no hurry. I’m using linux515 and that fails as well.
Fixed today with the linux515 update.
Many thanks for your hard work.