The intel media driver was updated to 24.4.4 and I was hoping that the video hardware acceleration would work again on Meteorlake. Unfortunately not, as of Intel Meteorlake the hardware acceleration is completely broken. Intel Arrow Lake also seems to be affected.
After this update, I experienced the system freeze when suspending my system due to freezing the user session, as previously described in the known issues for 2024-10-01 and 2024-09-09. However, I had not experienced this issue until this latest stable update. I was able to work around it the same way, by disabling the freezing of user sessions.
If it’s helpful, I experienced the issue with both the 6.11.11 and 6.12.4 kernels. I also do not have an Nvidia card.
Seems like most everything went fine, except my webcam stopped working after the udpate. Currently documenting that process here Suggestions for a recently broken webcam?, will come back to this if I can get it resolved somehow, or some other meaningful update.
A minor issue I’ve noticed within Plasma’s System Settings is a 15-20 second delay/freeze after selecting Workspace=>Search=>File Search… every other settings option loads quickly except for Search (which defaults to showing File Search). I thought maybe it was a caching thing and the subsequent selection of it would be faster, but that thought was wrong.
I’ve had baloo disabled for a couple years now, so there is no indexing/database… it would be odd if not having it enabled created a more complex check for File Search to load slowly.
I previously had the freeze on suspend issue, but I resolved it by adding the following line to systemd-suspend.service (and other sleep/hibernate/etc. service files), in the [Service] section
This issue came back after this update, and I noticed that this line disappeared in these files after the update, so I tried doing it again to fix it. However, my computer unfortunately still is unresponsive when I wake it up from suspend
One difference from last time is that the update seemed to have moved me from kernel 6.10 to 6.12. This may be the culprit, so I’m going to test it with the 6.6 kernel which is the latest LTS. But I’d much rather use a newer kernel in order to use newer nvidia drivers.
I also tried disabling bluetooth and wifi, because this thread says it might have something to do with a mediatek wifi card, which I have, but not the exact model. However, this didn’t really solve the problem.
Journalctl was not helpful in identifying the cause. The last entry in the journals is
Dec 24 17:54:09 9a3eedi-linux kernel: PM: suspend entry (deep)
Meaning there’s nothing showing what could be causing an issue after waking up
EDIT: kernel 6.6 didn’t fix the suspend issue. At this point I’ll just disable automatic suspend, it’s too unreliable. What a shame.
EDIT 2: sadly, it seems that it was only a temporary fix!
After 6 days working as expected, pamac-manager started to segfault again
I didn’t change anything on my system since then, the only noticeable event was an update of Firefox and Chromium yesterday…
On the Lenovo Thinkpad P15 Gen2, with KDE Plasma and X11 session any GTK4 apps starts using discrete graphics (can be monitored via nvidia-smi). Described WA with settings GDK_DISABLE=vulkan or GSK_RENDERER=ngl solves this issue too.
I encountered an issue when upgrading yesterday, where after rebooting my displays stopped working (more specifically, starting sddm would flash the screen a few times followed by black).
By modifying the boot command in grub by adding a “3” at the end of the linux parameter line, I was able to login and check journalctl where I was greeted with:
NVRM: API mismatch: the client has the version 550.144.03, but
NVRM: this kernel module has the version 550.135. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.
I’m going to guess this was specific to my setup where I messed something up with the packages I have installed, since I wasn’t able to find anyone else in this thread reporting the same issue after a quick search.
I was on linux 6.12.
Upgrading to the latest kernel version (6.13) fixed the issue: