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

this? [Testing Update] 2022-02-01 - Kernels, Pipewire 0.3.44, Qt5, Mesa 21.3.5, Wine 7.0 - #31 by omano (EDIT 2 and 3)

This should not have happen, it removed the file discussed in link above. [Testing Update] 2022-02-01 - Kernels, Pipewire 0.3.44, Qt5, Mesa 21.3.5, Wine 7.0 - #36 by philm

My solution:

Result: exists no group called “sudo”
Therefore (as root):
groupadd sudo
usermod -a -G sudo "user"
and reboot. Voila.

1 Like

latest sudo (1.9.9-2) has “disable non-interactive auth”.

does that mean keyword “NOPASSWD:” is no more in-affect in sudoers file. :slightly_frowning_face:

today’s update: due to referred dependency uninstall kvantum and kvantum-theme-matcha was uninstalled


Finally Kvantum is gone here on xfce as manjaro-xfce-settings no longer requires it. Many thanks!

1 Like

I have to downgrade fontconfig and lib32-fontconfig to 2.13.94 as the upgrade to 2.13.96 changed all my conky, it doesnt horizontally fit on my screen. Is there some new configuration that I have to change somewhere?

Oh boy, Plasma 5.24 incoming!
Fasten your seatbelts!


updated some hours ago, no issues so far :slightly_smiling_face:

1 Like

One screen? Wayland? Night Color active?
I immediately caught one. I had it during beta testing but couldn’t find the culprit and now I figured it out. If you happen to use a laptop with an external monitor set as primary screen, plus Night Color activated, in Wayland it fails on boot and resets the primary screen to the laptop’s. But it happens only if there a proxy configured in Systemsettings. Without it, no failure occurs.

X11 ofc, are you crazy? :laughing:

1 Like

Ha, nope, it’s krazy :joy:

1 Like

@oberon kactivitymanagerd probably needs rebuilding, it’s still 5.23.5.

edit: Or dropping if that patch is already included in upstream 5.24.

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