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.
No issues with the default dbus selection here, although I did perform the update over TTY to be ultra-conservative. I never bothered switching from lightdm and I’ve also masked avahi-daemon.
I tried the update again today. Now I can reach SDDM, and the system appears to be fine.
Edit: I do not know how many Guild Wars 2 players are here, but the only issue I have is with this game now. Its launcher seems to cause a GPU hang on Wayland. Can’t switch to another TTY, but SysRq works.
On X11, the launcher is frozen, but still responds to input (entering password, and pressing Enter to launch the game proper etc.), and GPU isn’t hung.
An Arch user can confirm the same behaviour on two different machines, using Plasma:
Reverting today’s update with Timeshift fixes this issue.
I don’t know if this is an Arch (seems more likely) or a Proton problem. I’ve tested both official and GE versions of Proton.
For some reason initramfs generated on my laptop for linux 6.7 is very big, and I’m sure I have no specific options for 6.7 that differ from 6.6 or 6.1. Why is it so?
The size is absolutely ridiculous, feature ‘packed’ or not (it broke my /boot partition, I’ve had to move it to a larger one), seems it’s similar for all distros (certainly for arch and manjaro), I’m sure it’s because it’s 6.7.0 (the first official, still experimenting I guess), that’s not going to stay like that.