Welcome to a new issue of This Week in Plasma!
This week we released a public beta of Plasma 6.7, ready for testing. A last-minute virtual keyboard feature snuck in… and with that, it’s now frozen for further features, and focus will shift to polishing and bug-fixing for the next month or two.
Looking good! I’m just on the stable branch so I’m still waiting for 6.7 to hit stable, but I’m excited to try it out, it looks like there’s a lot of nice QoL improvements coming. I’m going to be honest, I actually prefer the simpler fade for notifications. So it would be nice if there’s a toggle somewhere to switch back to just a simple fade transition for notification popups rather than the new slide-in.
In fact there is: you can turn it off using the KWin debug console (search for “debug”) on the “Events” “Effects” tab.
Love the slide notifications and “Keep Above Others” on top level of the titlebar context menu !
Keep rocking !
You mean “slidingnotifications” in the “Effects” tab?
What no satanic ritual when one presses F6 3 times?
That slide in/out animation is really slick! Nice!
I did mean that, yes. Corrected my post!
Hmm okay. Good to know.
obviously that is the shortcut to launch KDoom
Would it be possible to make the “hide from screen casts” window rule permanent? Currently it only seems to apply to one instance of that window, but when you close it and re-open it its no longer hidden.
Yep, looks like that part is new for 6.7.
Really pleased to see sliding notifications re-implemented in Plasma 6.7. It’s one of those small touches that makes notifications feel much more polished. Thanks for bringing it back!
And when will full session restoration work under Wayland?
It should be a priority to ensure that full session restoration works flawlessly.
That is currently not the case at all. For example, programs are assigned to the activities and screens where they were previously located.
You always have to sort things out at the beginning so you can continue working properly.
Have to say DITTO to this.
I am tracking this as it is pretty essential for me as well.
I currently can’t restore full session because on X11 that does not correctly apply activity association, something the Wayland implementation will be able to do, so I am restoring applications for each activity separately.
Wayland support has been available for testing (guarded by flags) for a bit more than a year and the specification was officially approved earlier this year.
KWin (and Mutter) and Qt (and GTK) implementations have been adjusted and activated by default in April, so the respective next version will likely have it without needing to set anything.
Haven’t checked the state of Chromium but they’ve also had support for the draft spec for over a year so they might also have merged the update for the official one by now.
For Mozilla I’ve only found a ticket that tracks this. There is no mention of an implementation of last years final draft so they might not be able to finalize this as quickly as the others.
Unfortunately Firefox is one of the applications I really need this for, hopefully this lands before KDE Neon switches Plasma 6.8 later this year.
Let’s hope it happens this year.
A feature like that should really be the first thing to work.
For some of the components this is pretty certain.
The changes for Mutter, KWin, GTK, Qt and Chromium have been merged to their respective main branches, so it is just a matter which release they are in.
For KWin I would assume this to be in Plasma 6.7 in a few weeks, for Qt maybe 6.12 in September.
For Mutter most likely with GNOME 51 in September as it probably didn’t make it in time for 50 in March, for GTK I would guess 4.24 also in September.
No idea about Chromium and when this ultimately come in Electron.
There are implementations for SDL and wlroots (and used by Sway) currently in a draft state which might make one of their releases this year.
It has been worked on for quite a while.
As far as I can tell the first proposal was from 2018 and has continuously received feedback from stake holders, i.e. desktop/compositor developers, toolkit/framework developers and application developers, and undergoing revisions to address that.
Seems to have hit a fairly stable state in 2024 which resulted in being part of releases by all major players by early 2025 for widespread testing.
With apparently sufficiently good results so only minor adjustments were needed to be officially accepted earlier this year and likely making it into the next possible release for the respective component.
Personally I was most positively surprised by Chromium’s early participation in draft releases, probably reflecting not just need as an application but also as a framework provider.
