KDE boots to black screen after updates on amdgpu

Just updated KDE and now boots to black screen on amdgpu. I rolled back to a previous snapshot. These are the updates. I’m wondering if it’s mesa causing it? Anyone else with amdgpu have this issue?

lib32-mesa 1:24.2.7-1 -> 1:24.3.1-1
lib32-vulkan-radeon 1:24.2.7-1 -> 1:24.3.1-1
lib32-zlib 1.3.1-1 -> 1.3.1-2
libwacom 2.13.0-1 -> 2.14.0-1
mesa 1:24.2.7-1 -> 1:24.3.1-1
sof-firmware 2024.09.1-1 -> 2024.09.2-1
sqlite 3.47.1-1 -> 3.47.1-2
vulkan-radeon 1:24.2.7-1 -> 1:24.3.1-1
zlib-ng 2.2.2-2 -> 2.2.2-3
1 Like

I updated ignoring mesa and the desktop loads properly so I’ll take that as being the issue. I’ll wait for another update to mesa.

2 Likes

Were you using/testing with X11 and/or Wayland?

After updating a VM, I encountered black screen when logging into a Wayland session. Logging in to X11 is working though. Not sure if it’s related, or VM specific though.

Same here… Black screen after updating… This happened on wayland… Tried removing my kwin config to see if that was the problem. It didn’t help. Can login into good old x11 though, thankfully!

1 Like

Same here. Also black screen both on wayland and x11 after reboot

Curious it’s affecting both in your case. What desktop environment are you using @mhusmann?

mesa 24.3.1 gallium crash/segfault

LM: sddm 0.21.0 (Wayland)
DE: KDE Plasma 6.2.4
WM: KWin (Wayland)

You might try running:

sudo downgrade mesa

Then select version 24.3.0-1 from the list, install and reboot.

I can confirm this fixed the issue for me.

You might note, that you’ll be given the option to add mesa to the IgnorePkg list in /etc/pacman.conf. If you say yes to this, all future updates for mesa will be ignored until you remove it from that list.

I just did so. It works. Thank you

1 Like

I am using Wayland. I didn’t bother switching to X1. I just ignored mesa and updated the rest. Until a new mesa is released I’ll wait.

I have not been able to detect any errors after an update. Same mesa and vulkan version as you are using and after reboot everything was fine

Perhaps it’s hardware specific and that’s how it passed testing?

That will be the point!

Ran into the same issue on Virtualbox VM. Downgrading mesa helped.

This is the second time that a mesa update has rendered the system unusable. Shouldn’t we find a replacement for this plague? It can’t be that we have to expect problems like this with every mesa update.

And what if, for some reason, you want to do a new installation right now? You get this crap served up online and you boot straight into a black screen when you start it for the first time. The alternative (offline installation followed by ignorePkg = mesa) is not an option for some reason.

I have a similar issue, black screen on first boot, then did an Syyu, got to log in, and eventually things worked. Guessing it’s fixed now?

Edit: Definitely not fixed. Even with the downgrade, it’s slow and my taskbar is missing…

My hardware is nothing special. It’s a desktop with amd cpuy and amd gpu RX590.

Edit: I can say and I will say we’ve had this a few times before with mesa updates. It’s the same thing. Login screen comes up and then when you try to log in there is no gear running and it’s just a black background with Welcome app showing up.

Nearly the same on my PC.
AMD Ryzen 7 5700G with Radeon Graphics. I have the GPU deactivated in BIOS
AMD Radeon RX 6600

I have never had an error like the one you described with any mesa update.

Anything can be possible. I just wanted to let you know that everything went well for me