Ok, I think I've got this display card under control - or so it seems. It hasn't crashed since Wednesday.

I guess this is a combo AMD RDNA3 Navi23 and KDE Plasma (+ Wayland?) bug...

I backed out all my Linux kernel command line switches for AMD GPUs and it crashed to green screen in less than a half hour. So, re-adding them stopped that from happening.

... amdgpu.dcdebugmask=0x410 amdgpu.tmz=0 amdgpu.gpu_recovery=1 amdgpu.sg_display=0 ...

And then the cursor thing is fixed <?!> by adding

KWIN_FORCE_SW_CURSOR=1

Currently this is what is set:

`cat /proc/$(pidof kwin_wayland)/environ | tr '\0' '\n' | grep KWIN` :

KWIN_DRM_NO_AMS=1
KWIN_DRM_NO_DIRECT_SCANOUT=1
KWIN_FORCE_SW_CURSOR=1

From a user experience point of view I don't see any difference with that software cursor setting.

There's another wrinkle to this that might be a factor but I can't really test around it currently. This is a multi-head machine and one screen is connected via HDMI and one is DP.

Perhaps this wouldn't be a problem if both screens were connected via the same type of connector.

Both screens are set to the same refresh frequency. But, in the display control app one reads back at 60.00 Hz while the other is 60.000 Hz. Minor thing right? But in trying to make this work I've seen references to AMD GPU weirdness in multi-head configurations where the refresh rates were different between screens. Red herring perhaps.

Anyway, don't know if there are (or will be) any people trying to make a RX 5800 XT GPU behave under Linux but this seems to be what worked for me and my dual head setup. I'll update if anything changes.

#Linux #AMD #AMDGPU #KDE #KDEPlasma #Plasma #AlpineLinux #kwin #Wayland

This morning I did get #kde #plasma #wayland up and running, had first fight with #sddm , this for my old monitors had really big colour difference, one darker and a grey/yellow taint. So I thought one of the monitors was breaking down, I spent weeks to looks for what next and spent money on new monitors. I have the same issue, so I decided to switch #Xorg for wayland, sure the issue is till there... and gosh wayland ain't the best on handling sessions IMHO, as which VT seems to be a bit randomish, you are stuck with "Switch User" and gosh it's SLOW like hell and easy to make plasmashell to crash on a session you are switching to. sddm don't allow you to specify the VTs you want to use, not even which VT to start with.

Plasma had the nice feature where you could scale old #X11 applications that don't have built in scaling, but then it would affect all X11 applications, this should have been a Special Window/Application rule, then it had been a lot more useful. Enabling #HDR , it works just for one monitor.

When #plasmashell crashes when you try to switch back, the view port seems to change to something a lot smaller. I can't get #yakuake to appear (either it's for it's far outside the view port or shift-f12 don't work when plasmashell wyaland crashes (in Xorg it works and the view is still full resolution).

It feels like everyone nowadays only develops a single user experience, desktop manager that can't handle multiple session (darn I miss #KDM , best ever desktop manager), desktop environments just don't handle that they aren't active. Multi monitor setups is nowadays a lot more experimental than it was in the 1990's.

As my main issue didn't get solved, I will revert back to Xorg and get a bit more stability. Maybe there will come something better to replace wayland, once in the time I was enthusiastic about it, but with time I just think it's just been a waste of time which could have been spent on gutting out all the old in Xorg and add new features.

I was made aware of the libinput debug-gui which looks perfectly fine even while I am in the error state.

During my experiments I found out I can make xournalpp crash by rolling the stylus on the drawing tablet. Thus I have acquired a core dump that I don’t even know where to post. Does it belong with the #xournalpp people or the #plasma people or the #wayland people or ???

just downgraded to 5.3.1, specifically, uh, "git 9069dbc".

not only i can open up the font dropdown menu, but also i can change the font of the text on the fly. tho it still feel finicky.

i can't change the font size in the paragraph tab, but i can in the character tab with or without selection.

#krita #kde #plasma

Has anyone able to change a font on #krita 6.0.1? Before, I couldn't open the dropdown menu. Now I can see my fonts, but cannot change the font of the text by selecting any of the fonts.

Operating System: #EndeavourOS
#KDE #Plasma Version: 6.6.4
KDE Frameworks Version: 6.25.0
#Qt Version: 6.11.0
Graphics Platform: #Wayland