KDE Plasma 6.3.1 just hit the Extra Repo.
Hurry hurry updating!
Took the update but never had time to play so far.
Another flawless update. Zero issues on an all-AMD rig.
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 Ă AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 62.4 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670 GAMING X AX
Maybe do not hurry yetâŠ
I have some issues:
Kicker wonât start
file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:21:1: Die Bibliothek /usr/lib/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so kann nicht geladen werden: libicui18n.so.75: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
and the Digital Clock widget is also broker atm:
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:16:1: Die Bibliothek /usr/lib/qt6/qml/org/kde/plasma/private/digitalclock/libdigitalclockplugin.so kann nicht geladen werden: libicui18n.so.75: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
Assuming youâve done the usual restart? Shouldnât be needed for non-kernel updates, but worth a check.
Log out or restart
Oh @Canoe put you in that direction
Full reboot was done, ofc. But I had some packages from testing repos on the system. I just
pacman -Syyuu 'd, will reboot now.
I never use widgets, so assuming that is an issue, it wonât affect me. Hopefully a reboot will do the trick for you.
rebasing on stable repos did the trick. After a
pacman -Syyuu
everything was working again.
Edit: Hurry on!
The digital clock in your panel also is a widget
Updated just now - allâs well.
These smooth updates are boring .
I should have been clearer. I meant desktop widgets.
Steam is closing and restarting itself after a few moments and also when i start a game. The game wonât start either. For the time being reverted to before the update.

Updated just now - allâs well.
These smooth updates are boring
.
Nice, huh? It didnât used to be that way. Before KDE 5, updates were a cross-your-fingers affair. It seems that every time Gnome (and sometimes Cinnamon) gets updated, there are tons of posts about something being broken. KDE Plasma has turned into the perfect DE, at least IMHO.
I know. I tried kde way-back-when, and kept trying it because i liked it, but, in those days, always went back to xfce, because of plasma being unstable or updates breaking the system.
So great to see KDE/ plasma becoming mature.
I hurried and I scurried to get the latest Kde updates. Canât get enough Kde!
I have to admit the KDE 6.3.0 messed up my PC a little bit for 20-30 minutes or so on Saturday, the fix was added in to 6.3.1, it was fixed on Monday after an update from KDE. Thankfully I check all my packages to see what is being updated before accepting them and noticed the major KDE package update was among them so I knew this was the culprit. Not really complaining, it was going to happen eventually, and not many people likely use colour profiles to come across this issue. And this was the first issue I got on Linux from an update so far in 8 months.
Regarding the issue, I have calibrated monitors and use my own calibrated colour profiles I created and the 6.3.0 made my screens go black with no cursor or anything with them enabled and restarting didnât help (I restart after every update anyway). You could log in and see SDDM but after that black screen and I would have to REISUB back to SDDM. I checked my secondary user account and found no issues (An example for why I have two user accounts for easy troubleshooting) so I knew it was related to KDE setting or something it was interacting with on my main user account. I ended up using TTY to rename the directory I store my ICC colour profiles so KDE plasma couldnât reach them anymore and then logging in to my account showed graphics on my monitors again.
This was the bug report for my issue if anyone wonders. As I update every Saturday I only had to wait 2 days for the fix, but the issue was reported before then on Tuesday.
https://bugs.kde.org/show_bug.cgi?id=499789
Good to see how quickly people triage and then find a workaround and then a solution.
Glad to know things are working again for you.
Despite my large block of text the issue wasnât really that bad to deal with too be honest, it was mostly a long message as I had to explain what the issue was otherwise the first paragraph wouldnât make sense.
Compared to some issues I come across in Windows, Microsoft services, and third party software in my job those break far more often than my linux system, and Microsoft in particular are so big you just have to wait until they fix as they donât really care about individual people reporting an issue, which could be months sometimes, or a few hours to implement their âworkaroundâ, or you have to keep contacting them and going through their escalation repeating the same things again and again, Microsoft forums are worse than any linux forum Iâve been on too.