WARNING: The plymouth-encrypt and sd-plymouth hooks no longer exist in the package. You should replace them with encrypt and plymouth hooks in your mkinitcpio.conf. The lxdm-plymouth.service, lightdm-plymouth.service and sddm-plymouth.service systemd service files no longer exist in the package. You should enable lxdm.service, lightdm.service or sddm.service instead.
Initramfs image can be bigger on 6.7 kernel due to Nvidia GSP Boot firmware
To reduce size add fallback_options="-S autodetect -S kms" to /etc/mkinitcpio.d/linux67.preset
Making dbus-broker our default D-Bus daemon
2024-01-09 - Jan Alexander Steffens
We are making dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.
For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. Pacman will ask you whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.
For a more detailed rationale, please see our RFC 25.
pacman-contrib is now split out from pacman. If you have anything installed that depends on pacman-contrib, update with:
sudo pacman -Syu --asdeps pacman-contrib
Additional Info
Info about AUR packages
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.
For help with AUR packages, please create a new topic in AUR and a helpful volunteer may be able to assist you.
I’m actually on testing branch but I would like to share a hint regards mesa update:
I have Intel HD Graphics 530. After removing the intel driver xf86-video-intel (and therefore switching to the modesetting driver) I could successfully update to 23.3.2 in Arch. Before removal of this package the boot process stucks with a black screen after updating from 23.3.1 to 23.3.2. This might be the same for some Manjaro users on Unstable.
I had somewhat similar experience last year. video-intel driver sees updates quite seldom, the latest version, for instance, was built almost a year ago. It doesn’t age well esp when combined with fresh mesa. At least that’s what I learnt the hard way.
Yes, thanks, removing xf86-video-intel (and using modesetting instead) allowed me to update to mesa 1:23.3.2 and boot successfully. I do have an older computer (12 years old), but it seems to be working well with modesetting.
For those seeing this on Intel, this is happening because your setup is broken and falling back to software rendering. If you have a very old system, you can use the intel ddx along with mesa-amber (NOT mesa!), for setups less than 10 years old, you should be using the modesetting ddx with mesa.
For nvidia, see NVIDIA - ArchWiki.
For VMs, please wait for a mesa update.
Yes, it’s a mesa bug, but almost nobody should be hitting it, as you shouldn’t be using swrast. We will revert a commit so even the “borken” systems should work again with an updated mesa package coming up soon …
We are making dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.
For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. Pacman will ask you whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.
For a more detailed rationale, please see our RFC 25.
I got new error messages after updating dbus and installing dbus-broker-units (Do not worry, they are harmless. You can ignore them)
$ journalctl --no-pager -p 3 -b -3 --output=cat
Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.knopwob.dunst.service'
Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service'
Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.knopwob.dunst.service'
A possible solution for KDE users:
Remove all duplicate files for example: You do not need org.knopwob.dunst.service
However, when you update dunst, this file will be overwritten again. You can add it to NoExtract to not overwrite it, if you want. But I would not do that for some reason.
But I got an error message:
Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service'
I didn’t get any errors or warnings during the dbus update, but I can’t reach SDDM after reboot. Problems with amdgpu perhaps, since the monitor loses signal. Happens on both 6.6 and 6.7 kernels.
I had to Timeshift via live environment, so I lost the logs.
Edit: To clarify, I did pick dbus-broker-units when asked by pacman.
No problems with dbus-broker here … but I replaced it shortly after install however long ago.
I also dont remember issues doing it on any longer lasting installs either though.
Don’t know what happened, after some tries to solve this problem, none of them worked, at least was the response in the chroot, and some reboots, it back to shows SDDM.
I tried to install dbus-daemon-units but pacman ended with “not possible to complete the transaction”.
Now my system is up and running. An old processor doing things, maybe.
WARNING: The 
