This week in KDE: real fake session restore

Welp, the mega-release is pretty much carved in stone now, and set for a release in four days! Lots of people have worked really hard on it for over a year, and we hope you love it! Nevertheless, I’m sure our diligent QA-obsessed users will waste no time in finding all the issues we missed, and we’ll work as hard as we can to fix them.

But once those are fixed too, the focus will eventually begin to shift once more towards features. And we have big ideas for new features to ship in Plasma 6.1 and beyond! With the architectural work done over the past year, a lot of very exciting possibilities have been unlocked. I think we’re going to see Plasma 6 as a pretty amazing springboard for next-gen stuff very quickly.

And to start things off, we have two nice new features that are landing in Plasma 6.1 already:

New Features

Even though we don’t have real session restore on Wayland yet (it’s still waiting for the protocol to be finalized), now we have the next best thing: fake session restore that simply re-opens apps you had open at the last logout and relies on them to have internally saved their own state appropriately. This works on X11 too (where apps that remember their window positions can do that as well), and it applies to all windows not covered by real session restore. As a result, now all your apps should always re-launch properly on login, rather than only the random-seeing assortment of session-restore-supporting apps re-launching on login. This feature is controlled by the existing setting that turns on or off session restore (David Edmundson, Plasma 6.1. Link)

In the Overview and Present windows effect, the way that windows are arranged is no longer configurable between two imperfect options: now there is only one layout algorithm and it’s waaaaaaay better than the old one! Windows are now arranged much more regularly and it ditches the very haphazard feeling of the old default algorithm, fixing multiple bugs causing weird window layouts including the infamous “stairway to heaven” arrangement (Yifan Zhu, Plasma 6.1. Link 1, link 2, link 3, link 4, link 5):

UI Improvements

When dragging a file or folder over another folder in Dolphin with the option turned on that opens the folder if you hold the dragged file there for a moment, the hovered folder now displays a little animation showing it open a bit (Felix Ernst, Dolphin 24.05. Link):

Headsets that report their battery status properly now benefit from a nice icon in all the places in Plasma that can show battery status (Severin Von Wnuck-Lipinski Plasma 6.1. Link)

The desktop context menu has lost its “Refresh” action which was infrequently used and did not actually fix most problems of missing icons that people might want to use it for. This makes the context menu lean and mean, and now nobody will have reason to say it’s “bloated” ever again! You can still manually refresh with F5 if needed (me: Nate Graham, Plasma 6.1. Link):

Bug Fixes

When connecting an iPhone or other Apple mobile device to your machine using a cable, and that phone has a name with an apostrophe in it (e.g. “Konqi’s iPhone”), now it works (Kai Uwe Broulik, kio-extras 24.02. Link)

Fixed the most common KWin crash on X11, which was commonly seen when the screen arrangement changed (Xaver Hugl, Plasma 5.27.11. Link)

Changing the Address, Name Style, Paper Size, or Phone Numbers settings on System Settings’ Region & Language page now actually takes effect (Timo Velten, Plasma 5.27.11. Link)

Fixed an issue that could cause the screen to turn black with only a movable cursor after switching from one virtual terminal to another one with certain graphics hardware (Jakob Petsovits, Plasma 5.27.11. Link)

Wind speed is now properly refreshed over time in forecasts provided by EnvCan in the Weather widget (Ismael Asensio, Plasma 5.27.11. Link)

Fixed a bug that could causing dragging-and-dropping Task manager icons to sometimes stop working (Fushan Wen, Plasma 6.0. Link)

KWin’s Zoom effect can now fully zoom into all areas of complex multi-screen setups (Michael VanOverbeek, KWin 6.0. Link)

A process named “ksmserver-logout-greeter” no longer shows up in your Task Manager while the logout screen is visible (Akseli Lahtinen, Plasma 6.0. Link)

Fixed a visual glitch that could cause window outlines to become slightly disconnected from their windows at certain window sizes when using certain fractional scale factors (Akseli Lahtinen, Plasma 6.0.1 Link)

Fixed a visual glitch that could cause windows on rotated displays to be briefly rotated incorrectly after becoming visible when using the “Glide” effect (Vlad Zahorodnii, Plasma 6.0.1. Link)

Fixed a case where KWin could crash when using the relatively old 340-series of NVIDIA drivers (Vlad Zahorodnii, Plasma 6.0.1. Link)

Fixed a way that Plasma could crash when manually restarted using systemd (Harald Sitter, Plasma 6.1. Link)

The shortcut chooser in the panel configuration dialog now respects your Plasma style’s color scheme as expected (Marco Martin, Frameworks 6.0. Link)

Toast-style notifications sent by Kirigami-based apps no longer visually overflow when they have a large amount of text in them (Jack Hill, Frameworks 6.0. Link)

Other bug information of note:

Performance & Technical

Improved Dolphin’s startup time by between 2% and 17% (Felix Ernst, Dolphin 24.05. Link)

Automation & Systematization

Added an autotest to ensure the proper functionality of text field context menus in QtQuick-based software (Fushan Wen, link)

…And Everything Else

This blog only covers the tip of the iceberg! If you’re hungry for more, check out https://planet.kde.org, where you can find more news from other KDE contributors.

How You Can Help

Thanks to you, our Plasma 6 fundraiser has been a crazy success! I originally thought the goal of 500 new KDE e.V. supporting members was over-optimistic, but you’ve all proven me happily wrong. We’re now up to an amazing 850 members. Thank you everyone for the confidence you’ve shown in us; we’ll try not to screw it up! 🙂 For those who haven’t donated to become members yet, spreading the wealth via this fundraiser is a great way to share the love. 🙂

If you’re a developer… sheesh, take a break for a few days. You’ve earned it!

Otherwise, visit https://community.kde.org/Get_Involved to discover other ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

This week in KDE: longstanding issues crushed

This week the focus was on annoying longstanding issues, and a whole bunch of them are now history! If you’ve used KDE software for any significant amount of time, I bet you noticed and were annoyed by at least one of the issues mentioned below, and can now rejoice at their annihilation! This effort has dropped the number of 15-minute Plasma bugs to its lowest level ever–just 30. The Mega-Release will be shipped in under two weeks, and we want it to be as fabulous as possible!

Pre-Mega-Release

…But first, some bugfixes backported to Plasma 5.27!

Fixed a way that KWin could crash in the Plasma Wayland session (Xaver Hugl, Plasma 5.27.11. Link)

Files copied to the clipboard are now made available to sandboxed apps using the portal system, so you can paste them into those apps (Karol Kosek, Plasma 5.27.11. Link)

After opening your laptop’s lid, the brightness of its backlit keyboard is now correctly restored to the same value it had before the lid was closed (Werner Sembach, Plasma 5.27.11. Link)

KDE 6 Mega-Release

(Includes all software to be released on the February 28th mega-release: Plasma 6, Frameworks 6, and apps from Gear 24.02)

UI improvements

When a panel popup is open, clicking on an empty area of the panel will now close it (David Edmundson, link)

When you try out a Global Menu and all your apps’ in-window menubars get hidden, if you later change your mind and remove the Global Menu, all of those apps’ in-window menubars now re-appear automatically instead of remaining hidden until manually shown again (David Edmundson, link)

When any of your physically connected screens are marked as disabled, opening System Settings’ Display & Monitor page now always shows an enabled screen when it opens, rather than sometime showing one of the disabled screens (David Edmundson, link)

Added Breeze icons for OpenVPN and Cisco VPN configuration files (Kai Uwe Broulik, link):

Bug fixes

Important note: I don’t mention fixes for bugs that were never released to users; it’s just too much for me (it would probably be too much for you to read as well), and most people never encountered them in the first place. Because we’re in the middle of a big Plasma dev cycle, there are a lot of these bugs! So big thanks to everyone who’s made it a priority to fix them!

Fixed several common random-seeming crashes in Plasma’s Activities backend code (Harald Sitter, link)

Fixed a significant annoyance that would, in most distros, cause several types of files to be opened in the wrong apps by default (e.g. images opened in Okular rather than Gwenview) until the first time the user changed any of the file associations (Harald Sitter, link)

Fixed a visual glitch in Gwenview that could cause image thumbnails to overlap when using a fractional scale factor (David Edmundson, link)

in Spectacle, drawing annotations with a touchscreen or a stylus no longer draws additional random-seeming straight lines in weird places (Marco Martin, link)

Shift+dragging windows to custom-tile them now works even if you’ve set your keyboard to do something exotic like emulate the Caps Lock key when pressing both Shift keys together (Xaver Hugl, link)

Fixed a case where the cursor failed to disappear as expected in certain WINE games (Vlad Zahorodnii, link)

Fixed a memory leak seen in Spectacle when recording the screen (Aleix Pol Gonzalez, link)

Other bug information of note:

Post-Mega-Release

Gwenview now has a minimal “Spotlight View” mode in which all the normal UI is hidden, and all you see is the image and the window titlebar (Ravi Saifullin, Gwenview 24.05. Link):

Before you ask, no this is not my paintjob! But I do plan to use it as inspiration 🙂

The warning on System Settings’ Proxy page no longer inaccurately warns you that Chromium-based browsers don’t respect it, which isn’t true anymore (Someone going by the pseudonym “Chaotic Abide”, kio-extras 25.04. Link)

Fixed the most common crash in Discover for Plasma 6.1, and we’re scoping out options for fixing it for 6.0 as well (Ivan Tkachenko, Plasma 6.1. Link)

System Settings’ Screen Locking page now has a clearer UI for selecting times (Kristen McWilliam, Plasma 6.1. Link):

  • Standard durations
  • Custom duration with selectable units

There’s now a KWin window rule you can use for controlling the status of Adaptive Sync for individual windows (Ravil Saifullin, Plasma 6.1. Link)

Performance & Technical

KWin now supports direct scan-out when run in a nested manner inside another compositor (Xaver Hugl, Plasma 6.1. Link)

Landed some major performance improvements for thumbnail generation in Gwenview and file listing in general (Arjen Hiemstra, Mega-Release 6. Link 1 and link 2)

Landed some major performance improvements for Spectacle’s Rectangular Region mode (Noah Davis, Spectacle 24.05. Link)

The spacings used throughout Plasma and Kirigami-based apps are no longer based on font sizes, and are now simply hardcoded to various static values, as they are in QtWidgets-based apps. This should slightly increase visual consistency everywhere, and make it possible over time to build UIs with more predictability in their spacings. This is more of a long-term thing, but it’s an exciting first step! (Noah Davis, Kirigami 6.0. Link)

…And Everything Else

This blog only covers the tip of the iceberg! If you’re hungry for more, check out https://planet.kde.org, where you can find more news from other KDE contributors.

How You Can Help

Thanks to you, our Plasma 6 fundraiser has been a crazy success! I originally thought the goal of 500 new KDE e.V. supporting members was over-optimistic, but you’ve all proven me happily wrong. We’re now up to an amazing 825 members, blown past our stretch goals, and 1000 members by launch time seems like it might even be feasible. Thank you everyone for the confidence you’ve shown in us; we’ll try not to screw it up! 🙂 For those who haven’t donated to become members yet, spreading the wealth via this fundraiser is a great way to share the love. 🙂

If you’re a developer, work on final Qt6/KF6/Plasma 6 issues! Which issues? These issues. Plasma 6 is very close to a release and in a good state, but could still benefit from some final bug-fixing and polishing. And as I mentioned before, if you haven’t tried it out yet, please do!

Otherwise, visit https://community.kde.org/Get_Involved to discover other ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

This week in KDE: Inching closer

The KDE 6 mega-release is due in a little under three weeks! And folks have remained in diligent bugfixing-and-polishing mode, because we want this release to be as smooth and drama-free as possible! If you haven’t already tried it out, this is a good time to. Find all the bugs that are bugging you so we can hopefully fix them before the final release!

KDE 6 Mega-Release

(Includes all software to be released on the February 28th mega-release: Plasma 6, Frameworks 6, and apps from Gear 24.02)

UI improvements

KWin’s “Active screen follows mouse” setting is now gone; now the active screen is always the one with the cursor on it, or the last one that was tapped with a touchscreen. This turns out to be much simpler and it’s what we think most people wanted anyway, hopefully alleviating complaints about OSDs and new windows opening on unexpected screens (Vlad Zahorodnii, link)

You can now set the data range manually for “horizontal bars” charts in System Monitor and its widgets (Arjen Hiemstra, link)

When you use the System Tray’s “Always show all entries” option, now it actually does always show all entries, instead of sneakily keeping some of them hidden anyway according to some internal logic which was not obvious (Jin Liu, link)

Searching through clipboard entries is now case-insensitive (Yifan Zhu, link)

Bug fixes

Important note: I don’t mention fixes for bugs that were never released to users; it’s just too much for me (it would probably be too much for you to read as well), and most people never encountered them in the first place. Because we’re in the middle of a big Plasma dev cycle, there are a lot of these bugs! So big thanks to everyone who’s made it a priority to fix them!

Fixed an issue affecting the Plasma X11 session that could cause the screen to end up black with only a movable cursor when you wake your system from sleep while using an NVIDIA GPU with its proprietary drivers (David Redondo, link)

CPU temperature sensors now work for a variety of Intel and AMD motherboards where they didn’t previously work (Arjen Hiemstra, link 1 and link 2)

When System Monitor’s window opens in maximized state, de-maximizing it now returns it to its pre-maximized geometry as expected (Arjen Hiemstra, link)

In various Kirigami-based apps, double-clicking on a page to open it multiple times is no longer interpreted that way–because opening the same page multiple times makes no sense–which avoids accidentally breaking the app (Arjen Hiemstra, link)

KScreen is now smarter about choosing better-matching screen settings when told to make one screen mirror another (Yifan Zhu, link)

Buttons and scrollbars in the Sticky Notes widget are now always distinguishable no matter what color you choose for the background of the note and no matter what your system color scheme is (me: Nate Graham, link)

A couple of Plasma UI elements with text on them that weren’t previously translatable now are (Emil Sari, link)

When your Task Manager is set up to only show tasks from the current screen, now this still keeps working when you switch around your screen arrangement without restarting Plasma (Someone awesome, link)

Header text in System Tray applets now elides instead of overflowing with a small window size and very long applet text (me: Nate Graham, link)

Other bug information of note:

Post-Mega-Release

When you hit the Alt+Tab shortcut with no windows open, you’ll now see a nice “No open windows” message instead of a broken-looking task switcher or even nothing (Vlad Zahorodnii, Plasma 6.1. Link)

The ancient feature to add a spacer in your window titlebars returns! (Vlad Zahorodnii, Plasma 6.1, link)

Automation & Systematization

Added an autotest to make sure that loading Digital Clock plugins still works (Fushan Wen, link)

…And Everything Else

This blog only covers the tip of the iceberg! If you’re hungry for more, check out https://planet.kde.org, where you can find more news from other KDE contributors.

How You Can Help

Thanks to you, our Plasma 6 fundraiser has been a crazy success! I originally thought the goal of 500 new KDE e.V. supporting members was over-optimistic, but you’ve all proven me happily wrong. We’re now up to an amazing 800 members, blown past our stretch goals, and 1000 members by launch time seems like it might even be feasible. Thank you everyone for the confidence you’ve shown in us; we’ll try not to screw it up! 🙂 For those who haven’t donated to become members yet, spreading the wealth via this fundraiser is a great way to share the love. 🙂

If you’re a developer, work on Qt6/KF6/Plasma 6 issues! Which issues? These issues. Plasma 6 is very close to a release and in a good state, but could still benefit from some final bug-fixing and polishing. And as I mentioned before, if you haven’t tried it out yet, please do!

Otherwise, visit https://community.kde.org/Get_Involved to discover other ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

15-Minute Bug Initiative update

A tad over two years ago, I revealed the 15-Minute Bug Initiative–an attempt to improve the out-of-the box user experience for Plasma by focusing on fixing obvious papercut issues. The idea was to crush the meme of “KDE is buggy” the same way we systematically addressed similar complaints like “KDE is ugly” and “KDE is bloated” in years past.

Well, it’s been two years, so how did it go? Let’s talk about it! First some numbers, because we like numbers:

  • Starting number of bugs: 92
  • Current number of bugs: 32
  • Total number of bugs fixed (because more were added over time): 231
  • Percent of all total 15-minute bugs that have been fixed: 87.8%

(note if you’re from the future: if you visit those links, some numbers may be different–hopefully lower for the second one and higher for the third one!)

Wow! That’s quite a few. So this initiative looks like it’s been a real success so far! Nevertheless, 32 bug reports remain open, so we can’t declare victory yet. These are some of the stubbornest, hardest-to-fix bugs that require major re-architecting, working upstream, or similarly challenging efforts. Hopefully the pace of improvement seen over these years has managed to convince you that they’ll eventually be resolved as well.

“Wait a minute, Plasma is still buggy AF you n00b”

Keep in mind these aren’t all the bug reports in the world we can fix (there are over 5000 of them for Plasma and Plasma-aligned software alone), just the ones I and some others have deemed to be most obvious to the average user! If you’re not an average user because you have three monitors arranged in a weird shape, each plugged into a different GPU from a different vendor and its own different DPI, scale factors, and custom Plasma panels, plus 4 activities and 9 virtual desktops and 6 internal disks, only half of which automount, and 12 apps set to autostart, and each of them is installed onto different disks, 15 window rules, and finally a custom theming setup including Kvantum themes and Aurorae window decorations… then yeah, you’re probably going to experience some more bugs compared to a more typical user who doesn’t have such a complex setup!

That’s okay. We care about you too, and we do work on those kinds of more esoteric bugs because many of us also have complex setups! But progress here will be necessarily slower, because the complex setups are more varied, more unusual, and harder to debug. And let’s be honest here: those of us with setups like these are experts capable of working around most bugs we find, who really should be helping to investigate and fix them. Admit it, you know it’s true!

But in a way, this is good: it represents Plasma moving from “It’s generally buggy” to “it’s specifically buggy–buggy with only certain less common combinations of settings, rather than buggy in a way that anyone can find within 15 minutes of using a system with its default settings. Improving on that was the point of this initiative.

Next steps

Up until now we’ve been ignoring Wayland-only bugs here, because the Wayland session was not the default one. Well, with Plasma 6 that changes, so all of those Wayland-only issues that meet the loose criteria to be a 15-minute bug will be promoted. Similarly, current 15-minute bugs that are X11-only will be demoted. So sometime in the next few weeks, expect the list to shift around a bit.

Once the number gets down to 0, it will of course go up again periodically as new bugs are found or introduced. But this is great! It means we can whack them as they appear, rather than letting them pile up over time. In this way the list becomes a “rapid response needed” task list rather than a backlog we’re always behind on.

What happens with those development resources once the 15-minute Plasma bugs are under control? I have a plan, first articulated in the original announcement 2 years ago: extend the program to Frameworks bugs! There are quite a few candidates there too. And because frameworks bugs can affect Plasma and our vast app library, quality will go up overall.

Speaking of those apps, once the 15-minute Frameworks bugs are also down to zero or close to it, we can include app bugs. This will finally give us complete coverage! I have a dream that one day, we’ll have a stable and mostly bug-free UI layer and our limited development resources can be focused more on performance work, sustainably-crafted new features, usability, more standardized styling, etc. I think it’s doubtful we can get there while we’re still battling routine bugs all the time.

How you can help

As always, help work on the existing 15-minute bugs if you can! If not, it’s always useful to work on bug triaging, so that more of those issues that will eventually become 15-minute bugs can get discovered. Another impactful way is to donate to KDE e.V., the nonprofit that support KDE on a ridiculously small budget. We’re still running the Plasma 6 fundraiser which represents a great way to donate!

What’s going on with Activities in Plasma 6?

Nothing! That’s the end of the blog post! Go back to what you were doing!

Well, sort of. 🙂 Some of you may be aware that a year or so ago, there was a lot of chatter about what to do with the Activities feature in Plasma 6: change how it works, remove the feature, or leave it be.

There’s broad consensus within the KDE developer community that the Activities feature doesn’t work the way we want it to. Its scope is conceptually unclear, it’s a frequent source of bugs, and it isn’t really maintained. As a result adoption in even our own apps has been low. It was for these reasons that over time we removed many of the entry points for Activities in the UI, and why I eventually proposed removing it entirely.

However the best way to to find out how many people are using something is to remove it! And the second best may be to propose removing it. 🙂 Many people showed up to offer their passionate pleas to keep the feature, explaining what they were using it for. Interestingly, many admitted that the feature didn’t really work very well out of the box and that they had done custom work to bend it to their use cases.

For this reason, several people stepped up to propose an overhaul of how Activities works, taking into account how the feature’s users actually use it. A lot of discussion ensued, and a few changes were merged. One was that Activities migrated from Frameworks to Plasma, which stripped it of its API guarantee and opens the door to us making major changes within the Plasma 6 lifecycle. Another change was to remove the per-Activity power management setting.

Unfortunately not much happened beyond that. As a result the status quo remains largely in effect for Plasma 6: the Activities feature has not been removed, overhauled, or even substantially bug-fixed. It remains a quirky and somewhat buggy DIY feature for adventurous users to build custom workflows around, and today it’s more hidden-away than ever if you don’t want to use it.

However, I don’t expect this to continue in the long term. Once Plasma 6 stabilizes and development resources are pulled off constant bug-fixing, attention will inevitably turn to Activities once again. So consider this blog post notice that the feature is at risk of being eventually removed if people don’t step up to contribute technical work to either fix existing bugs, or else overhauling the feature to work differently.

Personally, I’d like to see Activities morph into a feature whereby each activity has a separate set of settings and config data, but access to all the same user files. On top of that, you would be able to configure individual apps you use in multiple activities (like music players) to use shared settings and config data.This way it would basically be the “profiles” feature that many web browsers have now, but applied automatically to any and all apps you want.

But, like all desires and ideas, that personal idea of mine means nothing without work to transform it into an implementation! So if you use and enjoy Activities, or think you’d like to if they worked differently, please get involved. We’ll need your help if this feature is to remain!

This week in KDE: converging on a release

Believe it or not, the mega-release is coming out in less than a month. So soon! For this reason, all hands are on deck fixing bugs and polishing everything up. Nonetheless, the next releases of Plasma and KDE apps are starting to accumulate some juicy improvements too! Read on to find out…

KDE 6 Mega-Release

(Includes all software to be released on the February 28th mega-release: Plasma 6, Frameworks 6, and apps from Gear 24.02)

UI improvements

When you drag a file in the Plasma Wayland session and it passes over another window during the journey to its final destination, the window it passes over only raises itself to the top when you stop moving the cursor for a full second–up from the previous value of one quarter of a second (Xaver Hugl, link)

Panels in “Auto-Hide” (or the new “Dodge Windows”) mode that are currently hidden no longer inappropriately show themselves when the system wakes from sleep or its screen configuration changes (Vlad Zahorodnii, link 1 and link 2)

Made some more improvements to the ranking of KRunner search results (Alexander Lohnau, link)

The gray groove in scrollbar tracks that shows up on hover has been removed, because it didn’t really add anything since the whole scrollbar area is already framed. In the future if and when we remove that frame, the groove may re-appear, though (Akseli Lahtinen, link 1 and link 2):

When using the Breeze Dark Plasma style or color scheme, Plasma widget popups no longer have a white-ish flash while opening (Niccolò Venerandi, link)

The Clipboard and Keyboard Indicator System Tray applets now hide themselves completely when they have nothing to show, instead of appearing in the expanded part of the system tray and just showing you some kind of generic “there’s nothing to see here, hurr hurr” message when clicked (Jin Liu, link 1 and link 2)

Made the colors and line weights of single-pixel separators and outlines throughout Breeze-themes KDE software consistent, as many were previously using subtly different colors and line weights (Akseli Lahtinen and Marco Martin, link 1, link 2, link 3, link 4, link 5)

Bug fixes

Important note: I don’t mention fixes for bugs that were never released to users; it’s just too much for me (it would probably be too much for you to read as well), and most people never encountered them in the first place. Because we’re in the middle of a big Plasma dev cycle, there are a lot of these bugs! So big thanks to everyone who’s made it a priority to fix them!

It’s no longer possible to crash Plasma by giving a virtual desktop an absurdly long name (Vlad Zahorodnii, link)

It’s now possible to use Alt+PrintScreen as a key combination for global shortcuts (Yifan Zhu, link)

System Monitor’s “Import Page” functionality once again works (Arjen Hiemstra, link)

Plasma tooltips now get their visual styling from the active Plasma style’s Tooltip SVG, instead of its Dialog SVG, which was kinda weird (David Edmundson, link)

Made a bunch of fixes and improvements for windows using fractional scale factors (Akseli Lahtinen and Kai Uwe Broulik, link 1, link 2, link 3, and link 4)

With the Breeze application style, those rare menu items with multiple lines of text are now displayed correctly (Ilya Bizyaev, link)

The kinfo command-line program now correctly reports your graphics platform (i.e. X11 or Wayland) (Harald Sitter, link)

Other bug information of note:

Performance & Technical

Fixed a bug affecting with certain GPU setups that could cause KWin to use 100% of a CPU core whenever anything was using PipeWire to record the screen–which is actually quite a lot of things, including window thumbnails in the Task Manager and Overview effect (Xaver Hugl, link)

the Kickoff Application Launcher is now hugely more performant and faster to switch categories when hovering the cursor over multiple list items quickly (David Edmundson and Nicolas Fella, link 1 and link 2)

Made multiple improvements to reduce the amount of blocking when browsing mounted network file systems (Sergey Katunin, link 1 and link 2)

The “Closeable” window rule now works in the Plasma Wayland session (Vlad Zahorodnii, link)

Post-Mega-Release

Spectacle’s text tool now lets you insert line breaks and wrap text (Noah Davis, Spectacle 23.05. Link)

KCalc now uses a more modern frameless style (Carl Schwan, KCalc 24.05. Link):

The Weather widget now displays the chance of precipitation for all data providers except for BBC, which doesn’t provide this information (I guess it’s easier to just assume the chance is 100% for any location in the UK) (Ismael Asensio, Plasma 6.1. Link 1 and link 2):

When you have more than one audio input or output device, the name of each one shown in the System Tray widget is now a lot more readable and comprehensible, and doesn’t include weird technical text that often made no sense (Harald Sitter, Plasma 6.1. Link):

Notifications showing file transfer or download jobs now have a clearer arrangement of buttons (Oliver Beard, Plasma 6.1. Link):

When you activate the logout screen by invoking a specific action (e.g. “Shut Down”), it will now act more like a confirmation screen and only show you that action plus a cancel button (me: Nate Graham, Plasma 6.1. Link):

Right-clicking on a panel now yields a menu item that says “Show Panel Configuration”, which is clearer than the old “Enter Edit Mode” (Marco Martin, link)

…And Everything Else

This blog only covers the tip of the iceberg! If you’re hungry for more, check out https://planet.kde.org, where you can find more news from other KDE contributors.

How You Can Help

Thanks to you, our Plasma 6 fundraiser has been a crazy success! I originally thought the goal of 500 new KDE e.V. supporting members was over-optimistic, but you’ve all proven me happily wrong. We’re now up to an incredible 738 members, unlocked both stretch goals, and 1000 members by launch time seems like it might even be feasible. Thank you everyone for the confidence you’ve shown in us; we’ll try not to screw it up! 🙂 For those who haven’t donated to become members yet, spreading the wealth via this fundraiser is a great way to share the love. 🙂

If you’re a developer, work on Qt6/KF6/Plasma 6 issues! Which issues? These issues. Plasma 6 is very usable for daily driving now, but still in need of some final bug-fixing and polishing to get it into a solid state by February.

Otherwise, visit https://community.kde.org/Get_Involved to discover other ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

This week in KDE: everything everywhere all at once edition

This week we’ve got quite a bit of everything! Mega-release UI improvements and bug-fixes, new features for post-mega-release software, more bugfixes for KF5 software, performance improvements, better internal documentation, and impactful ecosystem improvements. Let’s dive in!

Post-Mega-Release

KCalc now shows you the equation you just entered, in addition to the calculated result (Gabriel Barrantes, KCalc 24.05, link):

Spectacle now scans QR codes in screenshots and offers you the opportunity to open their links (Dinesh Manajipet, Spectacle 24.05. Link)

The Weather widget now shows weather alerts for U.S. locations using the NOAA Weather backend (Ismael Asensio, Plasma 6.1. Link)

System Settings’ Drawing Tablet page can now be used to configure pen or tablet buttons to act as modifier keys rather than trigger actions (Tino Lorenz, Plasma 6.1. Link)

KDE 6 Mega-Release

(Includes all software to be released on the February 28th mega-release: Plasma 6, Frameworks 6, and apps from Gear 24.02)

General info

UI improvements

It’s no longer possible to drag an app or window from the Task Manager onto another part of its panel, accidentally creating a launcher widget out of it (Niccolò Venerandi, link)

Scrolling over the volume sliders in the Audio Volume widget and System Settings page now scrolls by increments of the user-configured volume step, rather than either changing the volume by 1% per scroll tick or doing nothing (Yifan Zhu, link 1 and link 2)

In the Plasma Wayland session, you can now mirror two screens on System Settings’ Display Configuration page using a visible combobox, not just by the hidden method of dragging one screen on top of another one in the visualization area (Yifan Zhu, link)

Bug fixes

Important note: I don’t mention fixes for bugs that were never released to users; it’s just too much for me (it would probably be too much for you to read as well), and most people never encountered them in the first place. Because we’re in the middle of a big Plasma dev cycle, there are a lot of these bugs! So big thanks to everyone who’s made it a priority to fix them!

The critically important Wobbly Windows effect once again works while using the Zoom effect to zoom in on something. Never stop wobbling! (Vlad Zahorodnii, link)

On System Settings’ Cursors page, the preview of available cursor sizes is now sized correctly when using a scale factor above 100% (Yifan Zhu, link 1 and link 2)

Changing the name, icon, command etc for an app marked as a favorite in Kickoff now updates the item immediately, rather than any such changes only taking effect after restarting Plasma (Marco Martin, link)

Fixed a bug that could cause panels in “Auto-Hide” or the new “Dodge Windows” mode to inappropriately un-hide and become stuck in an un-hidden state when the screen configuration changed in certain ways (Yifan Zhu, link)

Fixed multiple issues causing keyboard shortcuts using numberpad number keys to not register correctly in both the X11 and Wayland sessions (Nicolas Fella and Eugene Popov, link 1, link 2, link 3, and link 4)

It’s no longer possible to somewhat awkwardly open the “Alternatives” popup for a widget multiple times (Niccolò Venerandi, link)

Other bug information of note:

  • 4 Very high priority Plasma bugs (up from 3 last week, though two are likely the same thing and in need of investigation and triaging). Current list of bugs
  • 34 15-minute Plasma bugs (down from 35 last week). Current list of bugs
  • 150 KDE bugs of all kinds fixed over last week. Full list of bugs

Performance & Technical

Improved the performance of certain config-lookup code used commonly through KDE software by 35-40% (Friedrich Kossebau, link)

Improved performance and GUI responsiveness of the System Settings app by a little bit everywhere (David Edmundson, link)

Improved Discover’s launch time a bit (Aleix Pol Gonzalez, link 1 and link 2)

Improved compatibility between NVIDIA GPUs and the way KWin handles screencasting, screen sharing, and generating thumbnails for windows (Xaver Hugl, link)

Fixes for KF5

KF5 software continues to get a few fixes:

The feature in Discover to delete the config data of a no-longer-installed Flatpak app once again works (Ivan Tkachenko, Plasma 5.27.10.1. Link)

Fixed a crash in Dolphin when using kio-admin to do privilege escalation (Harald Sitter, Frameworks 5.115. Link)

Automation & Systematization

Wrote a tutorial about using PyQt to produce KDE software using Python rather than C++ (Thiago Sueto, Helio Loureiro, and Dimitris Kardarakos link)

Work not in KDE that affects KDE

KDE contributors also made two notable contributions to the world outside of KDE this week, which will positively affect not just KDE, but others as well:

There’s now a standard cross-desktop “prefers high contrast” setting that lives in the settings portal. Expect to see support for this showing up in KDE software soon! (Dominic Hayes, link)

Chromium- and Electron-based apps gained support for the cursor-shape-v1 Wayland protocol, allowing them to show standard cursor shapes and sizes in the Plasma Wayland session (Ilya Bizyaev, link)

…And Everything Else

This blog only covers the tip of the iceberg! If you’re hungry for more, check out https://planet.kde.org, where you can find more news from other KDE contributors.

How You Can Help

Thanks to you, our Plasma 6 fundraiser has been a crazy success! I originally thought the goal of 500 new KDE e.V. supporting members was over-optimistic, but you’ve all proven me happily wrong. We’re now up to an incredible 695 members, unlocked both stretch goals, and 1000 members by launch time seems like it might even be feasible. Thank you everyone for the confidence you’ve shown in us; we’ll try not to screw it up! 🙂 For those who haven’t donated to become members yet, spreading the wealth via this fundraiser is a great way to share the love. 🙂

If you’re a developer, work on Qt6/KF6/Plasma 6 issues! Which issues? These issues. Plasma 6 is very usable for daily driving now, but still in need of some final bug-fixing and polishing to get it into a solid state by February.

Otherwise, visit https://community.kde.org/Get_Involved to discover other ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

This week in KDE: auto-save in Dolphin and better fractional scaling

We’re in the home stretch now!

Plasma and Gear apps have branched, which means anything committed to master and not backported is going into the next release after the mega-release next month. For Plasma, the next one is 6.1, and for Gear apps, it’s 24.05. Quite a few new features and UI improvements are starting to accumulate there! Here are a few:

Dolphin now periodically auto-saves its open windows and tabs, so you don’t lose state if the app crashes or the system is restarted unexpectedly (Amol Godbole, Dolphin 24.05. Link)

In Dolphin, you can now configure whether backup and trash files are shown when hidden files are made visible (Méven Car, Dolphin 24.05. Link)

In Dolphin, you can now pop out a split view pane into its own new window (Loren Burkholder, Dolphin 24.05. Link)

Fixed an issue in Dolphin that could cause it to freeze when you use it to duplicate the same file multiple times (Eugene Popov, Dolphin 24.05. Link)

Okular now supports displaying popup menus in certain kinds of PDF documents that include them (Alexis Murzeau, Okular 24.05. Link)

Spectacle now lets you use more placeholders for screenshot and screen recording filenames (Noah Davis, Spectacle 24.05. Link 1 and link 2)

The Networks system tray popup can now tell you a network’s channel in addition to its frequency (Kai Uwe Broulik, link)

KDE 6 Mega-Release

(Includes all software to be released on the February 28th mega-release: Plasma 6, Frameworks 6, and apps from Gear 24.02)

General info – Open issues: 237

UI improvements

Plasma’s global Edit Mode toolbar now has an “Add Panel” button that lets you add panels. With this located there, the desktop context menu has now lost its “Add Widgets” and “Add Panels” menu items since the functionality is fully available in the global Edit Mode. This makes the menu smaller and less overwhelming by default. Of course, if you want those menu items back, you can just re-add them. 🙂 (Akseli Lahtinen and me: Nate Graham, link 1, link 2, and link 3):

In the portal-based “Choose a screen/window to record” dialog, items are now chosen with a single-click, unless the dialog is in multi-select mode, in which case a double-click will choose one (because a single-click only selects it). Also, in multi-select mode, the items have little checkboxes in the corner so you know that you can select more than one (Yifan Zhu and me: Nate Graham, link 1, and link 2):

This dialog could still use more UI polish, which is being scoped out

Bug fixes

Important note: I don’t mention fixes for bugs that were never released to users; it’s just too much for me (it would probably be too much for you to read as well), and most people never encountered them in the first place. Because we’re in the middle of a big Plasma dev cycle, there are a lot of these bugs! So big thanks to everyone who’s made it a priority to fix them!

Powerdevil no longer fails to start at login when using the ddcutil-2.0.0 library and certain DDC-compatible monitors (David Edmundson, link). Note that we also have reports of new issues for people using ddcutil-2.1.0, but those are different and need separate investigation, which is ongoing.

Did some more work to ensure that visual glitches in QtQuick apps are minimized when using a fractional scale factor. There’s still more work to do for text and window outlines/shadows, but you should no longer see weird tearing-related glitches in buttons and icons (Arjen Hiemstra and Marco Martin, link)

Made KWin more robust when restoring settings for multi-screen arrangements when any of the screens are missing their EDIDs (Stefan Hoffmeister, link)

When using a weather provider that gives forecasts longer than 7 days (like EnvCan), the right edge of the Weather widget’s forecast never gets cut off when viewed in the System Tray (Ismael Asensio, link)

Your Plasma panels will no longer flicker oddly when certain full-screen games do something rather odd by repeatedly switching their windows between full-screen and maximized states (Xaver Hugl, link)

The “Window Type” window rule–which did not work on Wayland–has been replaced with a new “Window Layer” rule which works better for the purposes people typically use it for (Vlad Zahorodnii, link)

Other bug information of note:

Performance & Technical

Improved the speed of various config file lookups used very commonly throughout KDE software by 13-16% (Friedrich Kossebau, link)

Fixes for KF5

We’ve also got a few nice fixes for KF5 software this week!

Fixed an issue when moving or copying large number of files that could cause some of them to get skipped (and potentially lost) after skipping duplicated folders (Eugene Popov, Frameworks 5.115. Link)

Fixed an issue that caused folders inside network shares/mounts to be non-expandable in Details view (Alessandro Astone, Frameworks 5.115. Link)

…And Everything Else

This blog only covers the tip of the iceberg! If you’re hungry for more, check out https://planet.kde.org, where you can find more news from other KDE contributors.

How You Can Help

Thanks to you, our Plasma 6 fundraiser has been a crazy success! I originally thought the goal of 500 new KDE e.V. supporting members was over-optimistic, but you’ve all proven me happily wrong. We’re now up to an incredible 665 members and unlocked both stretch goals! It’s pretty humbling. Thank you everyone for the confidence you’ve shown in us; we’ll try not to screw it up! 🙂 For those who haven’t donated to become members yet, spreading the wealth via this fundraiser is a great way to share the love. 🙂

If you’re a developer, work on Qt6/KF6/Plasma 6 issues! Which issues? These issues. Plasma 6 is very usable for daily driving now, but still in need of some final bug-fixing and polishing to get it into a solid state by February.

Otherwise, visit https://community.kde.org/Get_Involved to discover other ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

The last few weeks in KDE: It’s coming… it’s coming… it’s coming

Wow, it feels like it’s been a while! And while many of KDE’s contributors have been enjoying some holiday and vacation time, quite a lot happened too! We’re getting pretty close to the projected February 28th release day for the KDE 6 megarelease, so all hands have been on the bug-fixing deck.

Overall we’re in good shape. Despite the large number of open bug reports, most are not serious, and I have confidence that we’ll get the remaining major ones done before the final release. Of course, the best way to make sure that happens is to help out!

KDE 6 Mega-Release

(Includes all software to be released on the February 28th mega-release: Plasma 6, Frameworks 6, and apps from Gear 24.02)

General info – Open issues: 238

UI improvements

It’s now possible to quickly apply a wallpaper to all screens at once (Prajna Sariputra, link)

You can now set a custom mouse pointer speed, just like you can for the touchpad (Denis Zhdanov, link)

Discover Notifier no longer appears in your System Tray (even just the inactive area) unless it actually has something to notify you about–which means you can remove it permanently by simply telling Discover to never check for updates automatically on System Settings’ Updates page (Yifan Zhu, link)

Breeze-themed buttons and text field now always have the same height so they’ll never look slightly different when adjacent to one another (Akseli Lahtinen, link)

Throughout KDE software, the way symbolic icons (i.e. those whose names end with -symbolic) are found has been improved: when a symbolic icon is not found and the system has to fall back to a more generic icon, you’ll now get a symbolic version of that icon if it exists (Joshua Goins, link)

You can now configure Plasma to turn off the screen at the same moment when it locks (Jakob Petsovits, link 1 and link 2)

Bug fixes

Important note: I don’t mention fixes for bugs that were never released to users; it’s just too much for me (it would probably be too much for you to read as well), and most people never encountered them in the first place. Because we’re in the middle of a big Plasma dev cycle, there are a lot of these bugs! So big thanks to everyone who’s made it a priority to fix them!

Ark now preserves extended attributes of files in archives when editing and saving their contents (Kristen McWilliam, link)

Fixed a file descriptor leak in Plasma that could cause it to run out of file descriptors and crash under certain circumstances (Moody Liu, link)

Fixed an issue that could prevent the GlobalProtect SAML authentication method in OpenConnect VPNs from working (Rahul Rameshbabu, link)

Night color can now co-exist with color correction using ICC profiles–at least in the Wayland session (Xaver Hugl, link)

When using the weather widget’s DWD weather provider, you’ll no longer sometimes see nonsensically high temperature values shown in the forecast (Ismael Asensio, link)

Tabs in the weather widget no longer sometimes overlap in certain circumstances (Ismael Asensio, link)

Plasma’s “Alternatives” popup now follows the opacity level of its parent panel (Niccolò Venerandi, link)

When showing a preview of the selected Task Switcher style, clicking away from the preview now closes it as expected in the Plasma Wayland session (Ismael Asensio, link)

Other bug information of note:

Performance & Technical

The colord-kde repo has been ported to Qt6, so that color management on X11 works too (Nicolas Fella, link)

Reduced the background CPU usage when moving the pointer (Xaver Hugl, link)

A wide variety of pieces of transient state in QtWidgets-based apps are now stored in the state config file, not the settings file used for persistent user-set settings. This is a part of a very vocal crowd’s favorite bug! (Alexander Lohnau, link)

Automation & Systematization

Added GUI tests to make sure several Plasma bugs don’t recur (Fushan Wen, link 1, link 2, link 3, and link 4)

Added an autotest to make sure symbolic icon fallback works properly (Joshua Goins, link)

…And Everything Else

This blog only covers the tip of the iceberg! If you’re hungry for more, check out https://planet.kde.org, where you can find more news from other KDE contributors.

How You Can Help

Thanks to you, our Plasma 6 fundraiser has been a crazy success! I originally thought the goal of 500 new KDE e.V. supporting members was over-optimistic, but you’ve all proven me happily wrong. We’re now up to an incredible 627 members and unlocked multiple stretch goals! The first one has been met, but the second one is still on offer. So if you like the work we’re doing, spreading the wealth via this fundraiser is a great way to share the love. 🙂

If you’re a developer, work on Qt6/KF6/Plasma 6 issues! Which issues? These issues. Plasma 6 is very usable for daily driving now, but still in need of bug-fixing and polishing to get it into a releasable state by February.

Otherwise, visit https://community.kde.org/Get_Involved to discover other ways to be part of a project that really matters. Each contributor makes a huge difference in KDE; you are not a number or a cog in a machine! You don’t have to already be a programmer, either. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

Does Wayland really break everything?

I’ve written some other posts on Wayland recently, and it’s time for another one! Feel free to skip it it you aren’t interested in a discussion of Wayland and platforms.

Many may be familiar with the now semi-famous “Wayland breaks everything!” document written by Probonopd–one of the core AppImage developers–panning Wayland because it isn’t a drop-in replacement for X11. And he’s in the news again for a new Github repo with the aspiration of creating protocols for functionality not currently available to Wayland-native apps that are intentionally missing in Wayland’s standardized protocols–which won’t work because lacking standardization means they won’t become a part of the platform that app developers can reliably target.

There’s a bit of chuckling and jeering over this in developer circles, but to regular people, the whole “Wayland breaks everything” charge might ring true, or at least seem like it contains a kernel of truth. Because from a certain perspective, he’s right: Wayland really does break everything that directly uses X11 functionality!

It’s just that this is the wrong perspective.

Look, if I said, “Linux breaks Photoshop; you should keep using Windows!” I know how you’d respond, right? You’d say “Wait a minute, the problem is that Photoshop doesn’t support Linux!” And you’d be right. It’s a subtle but important difference that puts the responsibility in the right place. Because there’s nothing Linux can do to ‘un-break’ Photoshop; Adobe needs to port their software, and they simply haven’t done so yet.

And it’s much the same with X11 and Wayland. Wayland wasn’t designed to be a drop-in replacement for X11 any more than Linux was designed to replace Windows. Expectations need to be adjusted to reflect the fact that some changes might be required when transitioning from one to the other.

Now, even though Wayland wasn’t designed to be a drop-in replacement for X11, it was certainly intended to eventually replace it. But this implies that it was intended from the start to do less than X11, and and that would be correct.

X11 was a bad platform

In ye olden days, X11 was a whole development platform. Your app that targeted X11 could use X11 to draw its UI with a built-in widget toolkit; print documents with an included print server; record the screen; set global keyboard shortcuts; and so on. This is all way before my time, but I get the sense that X11 was either originally envisioned to be a development platform for app developers, or else quickly morphed into one during its early days.

It didn’t work out. The built-in UI toolkit looked horrendous, even for the standards of the time. Apps that requested the same resources could stomp on one another and break each others’ functionality in ways that were impossible to fix short of uninstalling one of the apps. Features like printing withered because a window manager was really the wrong place to put that functionality and its later maintainers lacked the needed expertise or interest to maintain it. And so on.

UI toolkits like Qt and GTK quickly rose up to take over most of this sort of app platform middleware in a way that worked much better for users and was easier to target for app developers. We’re talking about the mid 90s here; it was a long time ago.

(Of course this is slightly unfair; lacking a print server isn’t what people complain about being missing from Wayland. It’s more like things like apps able to set custom window icons and move their own windows. These are the really hard cases; they aren’t present on Wayland because they were commonly abused by apps on X11 to cause unsolvable problems. It’s not an easy thing and there are trade-offs involved in bringing them to Wayland.)

Linux isn’t a platform

Anyway, the rise of UI toolkits necessarily fragmented the app landscape. Instead of developing for one target (X11), a FOSS app developer now developed for Qt, or GTK, or whatever, so we ended up with a lot of “KDE apps” and “GNOME apps.” Yes, these apps still probably worked elsewhere, but it was obvious what platform and toolkit they been developed to work best in. They might look and feel weird when run elsewhere, or certain features might not work well or at all.

And that’s where we remain today. Absolutely nobody writes an “X11 app”; their app may use functionality in X11 for something that there’s no better way to do, but the app will use Qt, GTK, KDE Frameworks, or whatever for 99.9% of its functionality.

It brings us to a potentially thorny topic: Linux isn’t really a platform either, any more than X11 succeeded at being one. Almost nobody writes a “Linux app”; making raw Linux kernel system calls is generally unnecessary because whatever UI toolkit you’re using wraps this functionality and abstracts it to all the different platforms that the toolkit supports. The toolkit ensures that it just happens to work on Linux too.

The real platform

So is all hope lost for cross-desktop interoperability? No. In fact prospects are better than they have been in a long time! Because today there is in fact an emerging platform; something that abstracts away even the app toolkits if you want to roll that way. I’m talking about Portals, PipeWire, and Wayland protocols.

Probonopd pans these as bolt-ons that you shouldn’t have to have running on your system, but I think this isn’t realistic. The model of the monolithic window server that offers all functionality failed decades ago. In its place, we have libraries and APIs that every FOSS developers can reasonably expect a modern system to be running.

The portal system offers a standardized way to present platform-native open or save dialogs, send notifications, open documents in other apps, print documents, take screenshots, record the screen, handle drag-and-drop, see if the user’s active theme is light or dark, and much more. The portal system uses PipeWire under the hood for a lot of this stuff, so you can expect that to be installed as well. And you can also expect most Wayland compositors–most notably the two most important ones KWin and Mutter–to support pretty much all publicly standardized Wayland protocols.

I think this is the platform: Portals-and-Wayland-and-PipeWire. Clearly we need to come up with a better name. 🙂 Maybe PW2. But if your app targets these, it will run on pretty much every modern Linux system. And the big two FOSS toolkits of Qt and GTK both have cutting-edge support for all of it. So use whatever UI toolkit you like.

Why now?

We’re hearing more about this recently because the transition is picking up steam. X11’s maintainers have announced an end to its maintenance. Plasma is going Wayland by default, following GNOME. Fedora is dropping X11 support entirely. We’re in the part of the transition where people who haven’t thought about it at all are starting to do so and realizing that 100% of the pieces needed for their specific use cases aren’t in place yet. This is good! Them being heard is how stuff happens. I wish it had happened sooner, but we are where we are, and there are a lot of recent proposals and work around things like remote control, color management, drawing tablet support, and window positioning. There will probably be an awkward period before all of these pieces are in place for all of the people. And for the those who really do suffer from showstopping omissions, I say keep using X11 until it’s resolved. No one’s stopping you (well, except for Fedora, so if this is you, don’t use Fedora. 🙂 The cutting edge should be fun! If it isn’t, try something else).

Wrapping up

In this context, “breaking everything” is another perhaps less accurate way of saying “not everything is fully ported yet”. This porting is necessary because Wayland is designed to target a future that doesn’t include 100% drop-in compatibility with everything we did in the past, because it turns out that a lot of those things don’t make sense anymore. For the ones that do, a compatibility layer (XWayland) is already provided, and anything needing deeper system integration generally has a path forward (Portals and Wayland protocols and PipeWire) or is being actively worked on. It’s all happening!