KDE Plasma 6.3.4 fixes 'the most common Plasma crash', now down to zero very high priority bugs

Work on the KDE Plasma desktop sounds like it continues to go very well, with some really important bug fixes arriving to make the experience a lot nicer. My favourite Linux desktop environment and what powers the Desktop Mode on Steam Deck.

In the latest This Week in Plasma blog post, developer Nate Graham noted how the final very high priority bug has been solved. For Plasma 6.3.4 the "most common Plasma crash" is finally solved, which could happen "when unplugging screens, especially with a dock involved in the process somewhere".

With Valve shipping Plasma 6.2.5 in the SteamOS 3.7 Preview, perhaps they might want to get that bumped up again to improve the Steam Deck Desktop Mode some more since docking is a rather common thing to do.

The KDE developers also managed to solve some common KWin crashes, fixed a severe crash in Breeze-themed apps introduced in Plasma 6.3.3 and various other bug fixes. For the upcoming Plasma 6.4 release (due out in June) they've also added in a few new features too like notifications in the history popup retaining their interactive buttons, KWin's "Fade Desktop" virtual desktop switching effect now has a customizable duration and more.

Plasma 6.4 also has an improved display configuration page where the screen arrangement view is hidden when there's only one screen (makes sense), and a much more obvious screen chooser at the top to make it clear what screen is currently selected for configuration along with any connected but disabled screens.

Some other bits for Plasma 6.4 that sound quite exciting:

• Massively improved performance when making screen recordings in Spectacle using the VP9 video format, which is used by default.
• Implemented support for the wp_fifo_v1 Wayland protocol.
• Implemented support for the Clipboard Portal.
• Made KWin more resilient against the issue of windows moving to strange positions when changing the screen arrangement or number of screens.
• Plasma's log output is pretty quiet now thanks to Christoph's hard work. Nonetheless, he continued that work to help get us to zero!

See more in the blog post.