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

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.

I got a warning: directory permissions differ on /usr/lib/mysql/plugin/auth_pam_tool_dir/

What should the correct permissions set be like?

If you saw this via terminal, it should print the difference in permissions in the next line.

Check pacman.log:

$ grep "directory permissions differ on /usr/lib/mysql/plugin/auth_pam_tool_dir/" /var/log/pacman.log  -A1 | tail -2
1 Like

A post was split to a new topic: Pamac segfaults when I try building anything from AUR

I updated right now, and when verifying file conflicts before applying the packages updates, it failed, I didn’t save the exact error message but it was because of the file /usr/lib/systemd/system-shutdown/nvidia.shutdown that I manually created from this message [Testing Update] 2022-02-09 - Kernels, Haskell, Cutefish 0.7, Deepin, Firefox, Maui 2.1.1, Systemd - #25 by DAC324

So I moved the file elsewhere, proceeded to update and it didn’t fail at the “checking for file conflicts” step this time, it updated properly, and then I checked and the file nvidia.shutdown was recreated.

I assume this is something that has been added in the packages updates, but I can’t figure where this file comes from. pacman -F /usr/lib/systemd/system-shutdown/nvidia.shutdown doesn’t output anything. What I’m sure is that it is exactly the same content as link above, and not my modified version which has different comment in the file (and that I moved elsewhere before update).

Does someone know if I’m hallucinating or if this file comes with a package/script from Manjaro?

//EDIT: I found it [pkg-upd] 510.47.03-5 (fc774f34) · Commits · Packages / Extra / nvidia-utils · GitLab

pacman -Qo /usr/lib/systemd/system-shutdown/nvidia.shutdown
/usr/lib/systemd/system-shutdown/nvidia.shutdown is owned by nvidia-utils 510.54-1
1 Like