Caramba!,
I got caught by the update in the middle of a simple update…hope nothing breaks.
Regards
“Good news, everyone!” (Professor Hubert J. Farnsworth’s)
Since I was working on something I didn’t want to restart the PC until today Sunday to have time to reinstall just in case. My PC started without any visible or perceivable problems.
Using pamac-manager for the update, I had an error that since pamac was unable to update /etc/dunst/dunstrc, the update would not be committed. I am running i3 on an Intel Celeron-based dual-boot PC.
Fixed it by uninstalling dunstify, which then is not available anymore to install. Probably should be automated.
Thanks for the new updates. Especially for KDE plasma 5.24.2.
I was thinking we will have to wait until KDE plasma 5.24.3 to be in the stable branch.
I want to tell you that I tested Kde plasma 5.24.2 with the testing branch the previous days. I checked the problem that we had with the user’s avatar picture in the previous Kde plasma 5.23.5. Now, with kde plasma 5.24.2, changing the avatar picture is good through KDE settings but the system always display an error message (An error has occurred) after requesting my administrator password. Can you check it and perhaps report it to the KDE developers ?
I had a similar issue, a conflict involving dunstify (sorry, it’s in French):
Analyse des conflits entre fichiers...
La validation de la transaction a échoué:
conflit de fichiers :
- dunst : /usr/bin/dunstify existe déjà dans le système de fichiers (appartient à dunstify)
and couldn’t simply uninstall dunstify, since it is required by many other packages installed on my system.
bluetooth-keyboards get recognized and connected but they are without function. i tried 3 keyboards, it’s the same behaviour at all three of them. bluetooth-mice still works.
I have some icky locale issues after updating. Updated with pamac from TTY. This for example results in gnome-terminal failing to run with error:
# Locale not supported by C library.
# Using the fallback 'C' locale.
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached
[Edit: fixed my problems. Used Manjaro Settings Manager to use the Locale Settings. They were empty as suspected. Set everything back the way it used to be. Saved. Regenerated initial ramdisk images with sudo mkinitcpio -P. No more errors. Everything back to normal.]
[Edit 2: updated a couple of other PCs also running Manjaro Stable/Cinnamon DE: no issues with those updates.]
Logs from problem below.
Corresponding errors in the pacman.log when generating the initial ramdisk image:
I used pacdiff to check for .pacnew files after updating. There was nothing new. /etc/locale.conf and /etc/locale.gen are back to normal (at least) after I used the Locale Settings in the Manjaro Settings Manager. No idea what happened. I am going to it a try on another PC now.
Plasma Wayland on NVIDIA has broken for me in this update. Just a black screen with blinking cursor. Installed gnome-shell just to test, and wayland works fine on that.
[ 168.525835] [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000600] Failed to allocate NVKMS memory for GEM object
Probably due to my dual NVIDIA GPU setup. I’ll update the post if single GPU fixes it.
Since the last update I have a strange dark stripe on Brave-Browser on the left in my favorite newspaper website. I’m not sure if the error is related to Plasma or Brave. Can not say exactly, but those color probably matches the color of global theming.
Hi! Unable to update. This is the last lines of the update via pamac:
Controllo portachiavi…
Verifico l’integrità dei pacchetti…
Caricamento dei file dei pacchetti…
Controllo conflitti tra file…
Inizializzazione del trasferimento non riuscita.:
file in conflitto:
dunst: /usr/bin/dunstify already exists in filesystem (owned by dunstify)
I’ve previously had issues with my AX200 bluetooth (Anyone else experiencing Intel AX200 Bluetooth being disabled in kernel515?), and found after this update that it continues to work… No errors in journal, and my bluetooth devices are still listed in the bluetooth plasmoid. Some thoughts that may be helpful…
I am using kde plasma manjaro, and although blueman is listed in pamac, I do not have it installed. Not sure if it’s a requirement for your distro, but perhaps blueman is where the problem lies?
I am also still on kernel 5.15 (5.15.25) and have not tried 5.16 kernels yet.