Bug 511033

Forgot to mention that this issue is also apparent in KDE Linux (Tested with today's release and an older release).

Please add the output of kinfo to the report for the system experiencing the bug. Thanks.

I see there's a (non-desirable) workaround with nomodset.

Slightly older KInfo, pretty close to the time from where it stopped working.

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.16.4-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
Memory: 9.7 GiB of RAM
Graphics Processor: AMD Radeon Vega 3 Graphics
Manufacturer: Acer
Product Name: Aspire A515-43
System Version: V1.03

(In reply to Greeniac from comment #3)
> Slightly older KInfo, pretty close to the time from where it stopped working.
> 
> Operating System: Fedora Linux 42
> KDE Plasma Version: 6.4.4
> KDE Frameworks Version: 6.17.0
> Qt Version: 6.9.1
> Kernel Version: 6.16.4-200.fc42.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 4 × AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
> Memory: 9.7 GiB of RAM
> Graphics Processor: AMD Radeon Vega 3 Graphics
> Manufacturer: Acer
> Product Name: Aspire A515-43
> System Version: V1.03

It specifically stopped working when I updated from kernel 6.16.0 to 6.16.4 along with mesa (no other QT/KDE packages from what I remember), and I don't think the new kernel had to do with anything because booting to the previous working kernel does not fix the issue, so that's why I believe it's a regression that mesa/amdgpu introduced. But the fact the GNOME works perfectly fine means that the regression breaks something that KDE uses but not GNOME.

And I forgot to mention that when it freezes, the display updates after some time, showing the wallpaper and/or cursor, then it shows maybe the desktop icons, then something else. And when moving the cursor, the changes only appear after the next update, and the time between each update is maybe 10-20 seconds. 

It's difficult to explain, I will try to record a video soon to show the issue clearly.

Calling it a freeze is probably not the best description, but I can't find a better way to put it. It just suddenly goes from the usual smooth splash screen to just completely still.

Setting status to "REPORTED"

Also the steps to reproduce:

Flash the newest KDE Linux image to a USB.
Boot the flashed USB drive.
Wait until it gets to the splash screen (The screen with the Plasma logo and spinning gear).

Expected behavior: Plasma should start normally and go to the desktop.

Observed behavior: In the said splash screen, the spinning gear will suddendly stop spinning and stay there for a long time until the next "screen update", which will happen usually after 20-30 seconds.

Also I probably didn't explain the "screen update" thing properly. What I mean by that is, when using let's say a 60hz monitor, the screen should update 60 times per second, and this is what happens in the beginning of the splash screen , and in SDDM, but when it gets "stuck", the screen will start updating once every 20-30 seconds, and that continues when it finally goes to the desktop, making the system very unusable.

There are a whole lot of
> [drm] Fence fallback timer expired on ring gfx
in your log from the Mesa issue, so I'm rather confident the problem is on the driver side. Please follow up on it there.
If you have a version of Mesa you can reproduce it in, and a version where it doesn't happen, you can try git bisect to find the problematic commit. It may take a while to do, but it's generally the fastest way to get such weird bugs resolved.

On a side note, pageflip timeouts like in your logs are always kernel bugs, we wouldn't print it otherwise. It may be triggered by an issue in Mesa though (in this case, rendering never seems to complete?)

Okay, this is strange.

About a year ago, Arch with KDE just wouldn't load in my laptop it would always get stuck in the splash screen, so then I just installed Fedora KDE to it which worked fine for months, until the 25.1.7 Mesa update which broke KDE Plasma and it failed the same way as Arch did a year ago.

 So I just assumed that it was an issue with Mesa. But, Fedora Workstation worked fine in the new Mesa update, so then I thought that maybe it had something to do with KDE Plasma, but I just tested Debian testing branch which has Mesa 25.2.6 which works perfectly fine in KDE Plasma.

So I think that I need to test out more distros and see which ones have the issue and what's the corelation between them.