With this update, I decided to switch to systemd hooks that came with 2025-12-08, so this post is probably more relevant to 2025-12-08. However, that thread is already closed, so I am posting here as it might still be useful. For instance, @campfirereverted back to udev while the problem was actually fixable.
When switching from encrypt to sd-encrypt hook in mkinitcpio.conf, it is also necessary to update /etc/defaults/grub because systemd ignores cryptdevice in GRUB_CMDLINE_LINUX_DEFAULT. It expectsrd.luks.uuid or rd.luks.name instead. Also, if you decide to use a different name rather than the default luks-UUID, you have to update /etc/fstab.
I also had udev.log_priority=3 and I removed it just in case. Tbh, I do not know if it still works with systemd and has to be replaced with something else. It is probably INFO by default anyway.
In addition, I discovered that, unlike udev, systemd does not take over the unlocked file systems from grub. My /boot directory is on the encrypted volume, so I have to unlock it twice: once for grub and once for systemd. At this point, I am not sure if it would be better to mount EFI as /boot rather than /boot/efi and move grub with initramfs images there or just revert to udev and wait for a better solution to appear. Apart from making grub unencrypted, which is arguably not a big deal, my EFI partition is rather small and I will have to be careful about installing new kernels and retaining old ones. (I would definitely prefer not to resize luks partitions.)
Update: encrypt did not take over the unlocked file systems. Instead, it was using /crypto_keyfile.bin by default to unlock. With sd-encrypt you have to specify the key location explicitly or use the different default location. See pheiduck’s suggestion below.
I tried the KDE Plasma liveISO in a VirtualBox VM. I can’t get it use the host’s screen resolution or to adapt the screen resolution to the window size. It gets stuck to 800x600 and I don’t see why (virtualbox guest additions are in place at least).
Once installed it works a little better as I can change the screen resolution directly on the VMs Plasma settings, but It doesn’t seem to care about window size changes or changes in the VirtualBox view settings.
I also noticed that a Plymouth service (plymouth-quit-wait.service) gets stuck and systemctl status state stays at “starting” rather than “running” or “failed”.
I’m 3 updates behind, and today I just did an update of my PC with an Nvidia 1080Ti running Plasma on Wayland.
Surprisingly, I haven’t had any issues
I did get issues updating steam-native-runtime on the AUR due to some unresolved dependencies, but I think that’s separate since it’s AUR-related and I can probably figure it out on my own (or maybe give it time to resolve itself)
1/ Have you checked your pacnew files? From 2012-12-08 Gnome X11 was removed and hooks in /etc/mkinitcpio.conf probably needs to be updated. I don’t have Gnome and have been running wayland for some time so just a guess.
I assume the warning come from having resume= in Grub entry but the computer is not sleeping and hence is unable to resume (a wild guess, I am far from an expert), so there should be a hook or order of hooks to change.
2/ Do you use encryption? There is a similar discussion further up this thread. If you think it’s a kernel issue, which kernels have you tried?
Since 2025-12-08 update, I am having problems with Nvidia Drivers. Tried to reverse to 575xx on the last update but it broke my system (rolled back using my snapshot).
So, I am 2 stable updates behind. What is the correct procedure to use 575xx instead of 580xx? Do I need to do the downgrade before or after the update?
I dont have minecraft…