I have never seen so many problems with plasma in 6.2.1

Desktop Environments Plasma
1

I have participated in providing stack trace for three bugs which I’ve never had to do before. These are minor issues. However there is a big one. When I transfer files to my NFS (NAS) it can freeze up the entire UI. Videos still play audio and I have to wait until all the files finish transferring before the desktop comes back to life. Whats crazy is there is nothing logged in journalctl. I’m thinking I might eos-shifttime back to the 14th if this is going to continue happening. Should I try LTS kernel before giving up? I know partial updates are bad but can I lock the package updates for plasma and continue updating my regular software?

2

I removed orphans and will run LTS for awhile and see if that helps before I revert.

3

I have never seen so many problems with plasma in 6.2.1

I can’t say that I’ve ever dealt with transfering files to an NFS (NAS). But I can say that for my general use (Video editing, image creation/editing, watching video files, listening to music files, and general day-to-day web use), 6.2.1 has been rock solid for me so far.

3 Likes
4

Had this happen 2 times already too. It was always when I clicked on the taskbar to switch to an application right after starting the file transfer (IIRC the first time was on Plasma 6.2 and the second time on Plasma 6.2.1).

But yeah, nothing gets logged giving any hints about what is happening and once the transfer completes everything is fine again so I haven’t done a bug report yet.

Mind you I have since done 100s of file transfers to my NAS over NFS and it only happened the 2 times when the task bar was involved.

5

My weekly update is due tomorrow, but all this Plasma talk is making me hesitant lol.

3 Likes
6

That makes me wonder if maybe I should use terminal to copy instead.

7

I saw Radeon and kernel updates on the Arch repos and decided to pull the trigger a day early.

So far, so good. Will let you know if I encounter any issues with 6.2.1.

2 Likes
8
3 Likes
9

…seems I and only a handful of others had a black screen issue with the plasma 6.2 update.
Narrowed it do to 4 packages

4 extra/plasma-workspace 6.1.5-1 → 6.2.2-1
3 extra/plasma5support 6.1.5-1 → 6.2.2-1
2 extra/polkit-kde-agent 6.1.5-1 → 6.2.2-1
1 extra/powerdevil 6.1.5-1 → 6.2.2-1

10

I have these with no issues. Are you on nvidia? One thing you could do is go into tty ctrl + alt + F1-F6. F7 brings you back to GUI. Run command journalctl -b -p err
other options instead of err could be crit,emerg,alert,warning. It might just tell you what is causing it and can be reported to KDE if it hasn’t already as a back trace.

11

my hardware experiencing black screen after momentary flash of desktop screen

Lenovo Legion T5 26ARA8
AMD Ryzen 7 7700
Radeon RX 6600
samsung s32ag55 monitor

12

AMD Ryzen 7 7700X
Radeon RX 7600/7600XT/7600M XT/7600S/7700S / PRO W7600]
A620M Pro RS WiFi
Asrock PG34WQ15R2B Monitor

All is well (and has been, since the beta days).

1 Like
13

yes, I was overlooking that the motherboard is also part of the combination of factors

I suppose driver versions and firmware also are to be considered. What am I missing though? OS and OS versions, desktop environment.?

Good to know what combination of factors DOES function 100%. The difficult part is becoming aware of what causes the actual bug to absolutely happen when a specific combination of hardware and software occurs. Beta testing is rather essential, you think?

MacOS scores a point for reduction in variables

14

Here’s an idea. Boot into a live cd. Does it work? Then maybe something is wrong with your install. I see a lot of people also having messed up configs for KDE specifically so one thing they will do is move them out of ~/ temporarily. I think there is .local/share and another elsewhere but I’m not sure. Oh yeah and of course they will create a new login which will have a separate home directory. If that works then you can narrow it down to a config file in your home directory.