Hello all,
The Fedora KDE Plasma Edition SiG is pleased to announce the release of KDE Plasma 6.7.0.
This release brings a slew of new features, and you can find the release notes here: Plasma 6.7 - KDE Community
The release does need testers though, to do so here are the links:
F43: Making sure you're not a bot!
F44: Making sure you're not a bot!
I see it was pushed to stable a few minutes ago.
Do you want issues people find with 6.7 reported in Fedora BZ or to KDE folks?
Hi, new user here. How does the update process work? Does it start in the testing branch (via the Bodhi link Steve provided) and then get pushed to stable once it reaches the required karma threshold?
Also, how can I know when it’s ready to install from the stable repos (dnf upgrade shows no update from Canada and in bhodi it shows pending → Stable; so how/where did you see it in stable) . And how can I test the Bodhi update in the meantime?
I only see “submitted for stable” for F44, not pushed yet? And F43 is a bit further behind.
The push comes when there is enough karma, 2 weeks has passed and not negative karma threshhold has been reached. THese gates can be by-passed for critical fixes.
Interesting so it truly has been pushed, like you said, but not reached stable status/stable mirrors yet.
For those who aren’t familiar with bodhi, here’s the command to install plasma 6.7. I’m also new to bodhi, so.. I also got a little lost.
fc44:
bodhi updates download --updateid FEDORA-2026-279229780a
fc43:
bodhi updates download --updateid FFEDORA-2026-2b36efabf2
sudo dnf install ./*.rpm
The reality is pushing the update to stable is just one part of the process for making it installable via a dnf update. Depending on lots of factors, it can take a day (or even more) for individual mirrors to make the update available for installation. If you absolutely, positively, need the update yesterday, pull it from the koji builds, or build it yourself.
I think kdevelop needs a rebuild bump for the Fedora 43 updates(?):
https://bodhi.fedoraproject.org/updates/FEDORA-2026-2b36efabf2
There’s 81 (vs 80) builds in the Fedora 44 bodhi update:
https://bodhi.fedoraproject.org/updates/FEDORA-2026-2b36efabf2
…and I am getting dep issues with kdevelop-libs:
Problem 1: cannot install both libksysguard-6.7.0-1.fc43.x86_64 from f43-build-side-140808 and libksysguard-6.6.5-1.fc43.x86_64 from @System
- installed package kdevelop-libs-9:25.12.3-1.fc43.x86_64 requires libprocesscore.so.10()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package libksysguard-6.6.5-1.fc43.x86_64
- problem with installed package
Problem 2: cannot install both libksysguard-6.7.0-1.fc43.x86_64 from f43-build-side-140808 and libksysguard-6.6.5-1.fc43.x86_64 from @System
- installed package kdevelop-libs-9:25.12.3-1.fc43.x86_64 requires libprocesscore.so.10()(64bit), but none of the providers can be installed
- package ksystemstats-6.7.0-1.fc43.x86_64 from f43-build-side-140808 requires libprocesscore.so.11()(64bit), but none of the providers can be installed
- installed package kdevelop-9:25.12.3-1.fc43.x86_64 requires libKDevelopSessionsWatch.so()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package ksystemstats-6.6.5-1.fc43.x86_64
- problem with installed package
- package kdevelop-libs-9:25.08.2-1.fc43.x86_64 from updates-testing is filtered out by exclude filtering
- package kdevelop-libs-9:25.12.3-1.fc43.x86_64 from f43-build-side-140808 is filtered out by exclude filtering
I was wondering how to get these bodhi updates tested when they haven’t hit updates-testing repo yet… I was reading the Fedora doc and I am pretty sure your commands weren’t in there.
I made my own repo for dnf. Probably not the “correct” Fedora way, but I wanted to contribute to testing this update on Fedora 43.
> cat /etc/yum.repos.d/f43-build-side-140808.repo
[f43-build-side-140808]
name=f43-build-side-140808
baseurl=https://kojipkgs.fedoraproject.org/repos/f43-build-side-140808/latest/$basearch/
cost=2000
enabled=0
skip_if_unavailable=True
Careful with that one. With plasma, you already have 95% of packages installed. But if you do this on the KDE Apps releases (~300 packages) you’re going to be installing ALOT of superfluous packages!
Usually, you wanna do sudo dnf up, not sudo dnf in. But that wouldn’t have worked for this release because of additional packages.
So tl;dr: It’s complicated 
We have a bit of a precarious state happening in F43. We can’t update Gear because of issues with gpgme, and if we do an out of band update (i.e. bumping kdevelop for the update) then it desynchs the release with rawhide. This is likely to get fixed after it goes stable.
I meant to rebuild KDE Gear 25.12.3 KDevelop so that it can pick up the libprocesscore.so.11
bump from libksysguard update in the koji side tag…
..but I can see I am adding noise.
Thanks a whole lot for paying attention to Fedora 43 w/KDE versions. Much appreciated!
Folks… My system just upgraded to Plamsa 6.7.0 and it’s not working. Screen goes blank and after a few minutes, it returns to the login screen. Fortunately Gnome is still working. This thread indicates the same problem. I’m having the same symptoms. Any thoughts if/when a patch will be released? F44 P6.7 No KScreen backend found
Thanks.
Ray
I just updated to Plasma 6.7, however I have this bug that my network manager is always asking my wifi password everytime I restarted. Is this a thing for Atomic (Kinoite)?
I have the same issue since using 6.7. It used to work great till I updated to 6.7.
I’m also on Kinoite.
It turns out, at least here for me, you have to go to the KDE settings - WiFi&Internet and type your password in there:
That was the only issue that I ran into as well. The password for the Network was lost after the upgrade to 6.7.0. and just like you, adding it back into the Network manager fixed it. Tested with multiple reboots.
Ive just found out that deleting mesa shader cache and radv cache on ~/.cache then reboot makes the whole DE start panicking, spamming applets errors, kwin failure and so on so on.
I was used to do this all the time with no issues before 6.7 rolled out, the only way i found to fix was to obliterate the user and make a new one, i wonder what will happen once a mesa update rolls out and invalidades the old cache to buildup a new one.
I managed to replicate this as i went rampage reinstalling my OS multiple times, its very consistent.
Have a look in the system and user journals for errors.
What do you find?
