Welcome to a new issue of This Week in Plasma!
This week we released Plasma 6.7, and the reviews are overwhelmingly positive so far!
Plasma is just getting more and more polished, this was a pleasant upgrade, thank you KDE developers!
One thing that confused me was that I wasn’t seeing the new “press and hold a key to see related characters” functionality.
I think I expected there to be some kind of toggle button in the System Settings → Keyboard page to turn it on. I couldn’t find any. It wasn’t until I decided on a lark to select the “Plasma Keyboard” in the Virtual Keyboard page and noticed that it started working.
Now that I think about it, it makes sense on a compartmentalization of technology level to organize it this way, but … it’s just not intuitive that I had to do that.
Maybe this is on by default in new user setups so it’s not an issue, I dunno.
I believe the intention is to eventually turn on Plasma Keyboard by default once all the kinks are worked out. Some distros do that already; I believe Fedora is an example.
We probably should have included a reminder about this in the release notes! I think all of us have it on and forgot we did that.
I’m glad y’all fixed the discover notifier borking out when updating via RPM Ostree lol. I wonder if that will resolve the strange issue I’m having. Very strange indeed.
Also having proper per monitor virtual desktops is a game changer. Now I can toggle my secondary monitor between various apps very quickly. Also playing with the new Oxygen theme. Looks super cool.
New badge for screen layout looking.
Reminds me something I forgot to look up under bugs / report and validate if it isn’t.
If you have for example 2 monitors and connect a 3rd you expect the order of the existing two to be respected, similarly if you remove one of the 3 you expect the other two to remain in the same order. Don’t think that’s always the case now.
Yes, Plasma is becoming increasingly refined, with a strategy of incremental improvements.
It’s amazing that Bug 499902 isn’t a top priority for the development team, since it ruins fundamental system features like the overview and grid view.
I’m not sure, but there might be some regression in KDE 6.7 and NVIDIA GPU, on a notebook.
I was using Fedora 44, and when I received the update to 6.7, I started noticing that the FPS in a game using Proton began to vary sharply and randomly between 60 and 30 FPS.
The same thing happens using Godot Engine, even though everything was normal before.
I also tried updating the NVIDIA driver from version 595.XX to the newest 610.43.02, available directly on the NVIDIA website, but the problem persisted.
After a few hours trying to solve the problem, I decided to install Kubuntu LTS, which has the KDE and NVIDIA versions that I knew were working correctly, and the problem was solved.
I can confirm that the following settings resolved my performance issue:
Operating system: Kubuntu 26.04 LTS
KDE Plasma version: 6.6.4
KDE Frameworks version: 6.24.0
Qt version: 6.10.2
Kernel version: 7.0.0-22-generic (64-bit)
Graphics platform: Wayland
Processors: 12 Ă— AMD Ryzen 5 5600H with Radeon Graphics
GPU 1: AMD Radeon Graphics
GPU 2: NVIDIA GeForce RTX 3050 Laptop GPU (595.71.05)
It seems that something in the last Fedora update between KDE 6.6.4 and 6.7 may have caused some performance regression.
Perhaps it has something to do with this problem?
Thank you for your attention and have a nice day.
Special key characters on long press works on Fedora KDE44 Plasma 6.7.0…yeaah. Tested with Kate and Thunderbird.
But Discover is borked…shows updates or none in the LHS but main window is stuck on updating. This greys out the “Update all” button, making it impossible to update via the GUI.
For the time being, updates have to be done via Konsole.
Love Oxygen. Finally getting away from the flat look that has become so prevalent.
I have this too. It can be bypassed by telling discover to ignore knewstuff by adding
–backends=flatpak,packagekit %U
to the start command in the application launcher.
Discover hanging in “Update” forever can be fixed by removing the backend “plasma-discover-snap”. So far everybody that has removed it had a 100% success of fixing the problem.
As a Fedora KDE User I traced mine back to its 1st appearance when I upgraded to Fedora 44 from Fedora 43. It was installed as part of the upgrade, despite that I had not installed any applet that required snap. It didn’t cause any problem then in Discover.
The problem didn’t appear until the upgrade from Plasma 6.5 to Plasma 6.7.0
As part of Plasma’s 6.7.0 installation “plasma-discover-snap” was also updated to a later version and that’s when Discover got broken.
For Fedora KDE Users to remove the package:
Open Konsole (bash) then copy/paste in:
sudo dnf remove plasma-discover-snap
Then reboot just to be sure and you should be good to go.
Its not just Fedora, other users using different distros have reported the same problem.
I have logged a bug report with bugs.kde.org
This has been fixed in neon now.
What fixed it in Neon? Can you track down the change?
Apparently some patches were backported? The new build of the package updated this morning fixes it. I have no idea where to locate the changes made, yet.
https://blogs.kde.org/2026/06/20/this-week-in-plasma-6.7-is-here/#notable-new-features:
Monitors are now identified with color-coded number badges in all the places they’re configured
I like this new feature! But in the screenshot, the visual representation of those number badges differs between different places:
To make them feel more connected, they should probably look the same everywhere.
Guys you were sending me on a long trip to frustration land.
I have a Keychron K5 keyboard. Each time I logged into either Endeavour or Arch, my keyboard backlight was changing from Red to Pink/white.
I did not notice it happens on login or shortly after. (I mainly focused on the screen, typing blindly).
I thought my keyboard has an issue. Factory resetted multiple times, restored my red solid color - then later on again it changed the color.
I used AI to search online for similar issues - I even booted into Windows to check for a firmware update.
Long story short - the new Keyboard color option to follow accent color did it. And I did not even know this is a new feature/option.
For the love of god, please do not auto-enable such new features. I was considering to throw my keyboard away over this as it pissed me off so much. (I’m already unhappy with the keyboard as I have recurring issues with the same 2 keys/switches)
Without AI pointing it out as it knows I’m on Linux with KDE Plasma, I would have not figured this one out as I usually don’t change the Monitor brightness via the slider in the same menu.
this update has had one really annoying feature, the “alternate characters popup” the fact this is toggled to turn on when holding down a key is a really mind mindbogglingly profound idea. it interrupts the regular key repeat behavior. there is no good reason for this to be turned on by default it is annoying and just gets in the users way, it really feels like nobody thought about how this may impact the average users experience.
I am sure this is a useful thing for those that need it although they are in the clear minority. i see no good reason whatsoever that this should be forced by default onto everybody OR why it should be binded to a behavior that is ALREADY taken by the key repeat.
now i understand that i can turn it off but i shouldn’t have to fiddle around with settings or spend time looking up how to turn it off, it should never have been on in the first place unless i specifically wanted it turned on.
this feels extremely sloppy just from a UI/UX stand point, in the future do not hesitate to take more time to test an update before just releasing so you can all prevent bugs like this from happening in the future, it would be greatly appreciated.
thank you.