Plasma 6 has come into its own over the last two releases. The wrinkles that always come with a major migration have been ironed out, and it’s time to start delivering on the promises of the new Qt 6 and Wayland technology platforms that Plasma is built on top of.
Plasma 6.2 includes a smorgasbord of new features for users of drawing tablets. It implements more complete support for the Wayland color management protocol, and enables it by default. There is also improved brightness handling for HDR and ICC profiles, as well as HDR performance. A new tone mapping feature built into Plasma’s KWin compositor will help improve the look of images with a brightness or set of colors greater than what the screen can display, thus reducing the “blown out” look such images can otherwise exhibit.
When it comes to power management You can now override misbehaving applications that block the system from going to sleep or locking the screen (and thus prevent saving power), and you can also adjust the brightness of each connected monitor machine separately.
Plasma’s built-in app store and software management tool, Discover, now supports PostmarketOS packages for your mobile devices, helps you write better reviews of apps, and presents apps’ license information more accurately.
In Plasma 6.2, KDE have overhauled System Settings’ Accessibility page and added colorblindness filters. They’ve also added support for the full “sticky keys” feature on Wayland.
This and more in full anounncement and changelog.
I activated it on my work laptop to benefit from a little more time to get bug reports upstream. OpenQA can’t catch everything. Even if I updated only once a month I’d still get up-to-date software at that time.
Sure, openQA and snapper make catastrophic failure very unlikely. But it’s still a small hassle.
But I can’t work anymore anyways so I might as well get all the good stuff as quickly as possible. Just gotta find the energy to switch the repos. By that time Plasma 6.2 has probably hit Slowroll. Let’s see.
Oh alright, I do see the point now! I had the wrong idea about how it works. I get the need to have more guarantees on functioning packages