This week in KDE: a metric avalanche of amazing things

Get ready for a massive load of improvement! And it’s all pretty darn shiny too because in addition to a ton of work on apps, we polished up Plasma to be as smooth as a marble for the 5.17 beta version (numbered 5.16.90), which is now available. The final product is due to be released in about a month, and as you’ll see, KDE contributors have been hard at work making it as awesome as humanly possible! A few things have slipped until the Plasma 5.18 LTS release, but that’s okay because it means 3 more months to polish them up.

Oh, one more thing before we begin: like Kate, Okular is now also available on the Microsoft store! This work is so important because Windows users who become accustomed to using free open source software on Windows are more easily able to switch to a fully FOSS platform, like a Linux distro running KDE Plasma. 🙂

New Features

Bugfixes & Performance Improvements

User Interface Improvements

How You Can Help

Do you like the idea of enticing Windows users by making KDE apps more available to them? If so, check out this post by Kate developer Christoph Cullmann. Relevant skills include build systems, packaging, and promotion It’s very important work, and a key part of the new “all about the apps” initiative.

You can also check out, and find out other ways to help be a part of something that really matters. You don’t have to already be a programmer. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

Finally, consider making a tax-deductible donation to the KDE e.V. foundation.

46 thoughts on “This week in KDE: a metric avalanche of amazing things

  1. Wow man! A whole lot of changes! That’s great. You guys are rocking!

    Synchronizing KDE ecosystem can greatly help users to get into using this platform in their devices.

    In my opinion, furthermore, you can create a page in to recommend some top distros which are running KDE, so users can easily find a way to install KDE on their systems. For example distros like KDE Neon, Manjaro KDE, Fedora KDE, Kubuntu etc. can be placed there.


    1. I seem to remember KDE officially being against promoting one distro over another. Even KDE Neon is not the “official KDE distro” that some assume it is and its FAW even say that it’s not a distro. On the products page, there is at least a button to see a list of distros that offer Plasma:
      BTW, you forgot openSUSE Tumbleweed and Leap, the best KDE distros 😉


    2. Thank you Noah. By saying that I was not going to say promoting any distro over another. I mean only help users to find out how to reach KDE easily and quickly. You know, some users maybe confused when they want to start using KDE, because Linux ecosystem is so massive.
      Also I see that button in KDE products page, that would be very helpful!
      And oh! sorry for forgetting to mention openSUSE! That one is a good example of a KDE based Linux distribution that I forget to mention!
      Thank you guys, hope to see more and more users in KDE community.


  2. Take THAT, Redmond! Seriously, when Plasma 5.18 comes around (and also Kubuntu 20.04), so much Windowsbutt will be kicked. It’s already kicked hard but next spring it’s kicked into oblivion. I mentioned Kubuntu because that’s probably the most used/famous one that will get a lot of attention upon release. Thanks again, buttkicking KDE warriors, for all your amazing work!


    1. Yeah I thought the 5.12 LTS was pretty good, but still had a lot of rough edges. By 5.18, it’s going to be amazing.


    2. I’m already psyched for 5.17. Seriously, while I really like the default settings of Kubuntu, KDE gets better so quickly I feel like I’m missing out if I don’t use Neon or non-LTS Kubuntu. I’m always torn between these two options, but in the end I like having an LTS ubuntu base (I have to use a lot of 3rd party apps and Ubuntu LTS is your best bet for a functional deb, Flatpaks help a lot, but many of them are still rough around the edges).


    3. I know exactly how you feel. KDE software in general is so stable and fast to fix bugs that I can no longer stand not using the latest version (or even git master, which I currently live on). Neon is great for this, but you need to deal with old versions of other apps and the supporting libraries, some of which also improve very quickly. Kubuntu non-LTS is better for that use case, but then you need to deal with old versions of KDE Applications due to the release schedules not lining up perfectly!

      Personally I’m happy with fully-rolling distros right now, but I recognize that they’re not for everyone, and the needs of a software developer differ from those of a user.


  3. Another Sunday, another great KDE week full of work by the KDE Community folks :).

    Plasma 5.17 really received a lot of love this past week, for its promotion to beta, i’m really pleased for that. But the fact that Plasma 5.18 is starting to show up, always makes me feel really overtaken, for the huge amount of work you’re doing every day, every week, etc.

    I can’t say thanks enough to everyone at KDE Community who supports, helps and makes all these awesome software possible. And of course, special mention as always for you Nate, working too and with the extra work of post it here at your blog every Sunday since 2 years ago, more or less. Just amazing.

    A huge hug to everyone mentioned above ^^.

    KDE Rocks!!!


  4. About show an icon for everything in context menu. I thought it’s more consistent to have for everything an icon in the menubar and connect menu. After two weeks I found out that have icons for the most used commands and for the rest only label improve the visual search, so libreoffice menubar has now only on most common commands icons.

    Liked by 2 people

    1. With some obvious exceptions (cut, copy, paste), aren’t the “most used commands” going to vary from person to person though?

      The problem of menus being too long is real, but I’m not sure I like the idea of emphasizing visual focus by omitting icons from certain menu items.


  5. Hey, Nate!

    Great work :-). Just one comment to the audio “default device” button. I get the impression that this button is more of a step backwards. KDE always got the reputation to be overloaded etc. By moving the “default” entry out of the easily accessible and tidy menu directly into the always visible volume slider popup, I – subjectively – think this helps the just mentioned reputation. Is it really helping the user a lot? I guess it’s meant for easier discovering of that functionality (because one single click more into the menu isn’t that bad for an action like that). If you look at your own work in the display configuration dialog, you replaced text based selections (the rotation) with icon based. Perhaps using an icon only – close to the menu button – would at least reduce the “messy” impression, if you still think that this functionality needs to be “on the top level”?



    1. Yes, a button with the “star icon” only and a tooltip would be sufficient and make it look less cluttered IMHO.


    2. I also find those buttons looking spammy. Windows for example just colors the background differently for the default device. Maybe Plasma can do the same, or just change the icon’s background if you don’t want to 1:1 copy from another system.


  6. Great job! Love to read your weekly updates.

    Hope that some day KDE devs will implement blurred transparency not only for menus and konsole, but for windows and topbars too (qtcurve isn’t working on my laptop anymore for some reason)

    Liked by 1 person

  7. I added kde-unstable to Arch Linux, and I did not find Kate 19.12.0 in the repo.

    I tried to type 12000 kilometres or 12000 km in the search box at the KDE start icon, but the result did not appear.


    1. Is there how to replace kicker for kickoff on Arch Linux?

      Ah, I have a suggestion: do not forget of upgrading the currency conversion for KRunner, because many currencies we want to convert do not exist in currencies list due to the outdate. I recommend you to use package units (check; Ulauncher has an extension called converter, in the which you will check the second screenshot, that shows you convert any of 200 currencies.


  8. Windows user here!

    Great to see Okular showing up in the Windows Store.
    Just a couple of things to note:
    Please use the Breeze icon in the Windows Store instead of that old icon.

    The Navigation Panel does not memorize my otion of showing small icons with no text. Every time I open Okular I need to change the size of the icons. This is extremely annoying.


    1. Hmmph. Actually Okular does not keep any changes to the default configurations that I made.
      Well, that’s sad. Time to uninstall and go back to closed source pdf readers.


  9. It is very nice to see how Plasma makes leaps every week and all its edges becomes rounder and rounder.

    I also like the idea to make the transition from Windows to Plasma as smooth as possible, however I think in the end this will only work on a lager scale if some equivalent key apps are available on Plasma (It’s all about the apps):

    * By far the most used apps: Excel, Word, PowerPoint: Yes, there’s LibreOffice, but sadly it cannot keep up with their proprietary counter parts. Then again, LibreOffice is GTK and not Qt and so definitely not part of the Plasma project.

    * For plasma mobile or touchscreens, a good OneNote alternative would really be appreciated. I know many many students who take notes on their Windows tablets with OneNote instead of writing on paper and they won’t change without an alternative.

    * I really hope that Wayland helps to reduce the system performance requirements during gaming, to motivate more players to onboard.

    “Our Compositor still gets damage events from other windows, it gets woken up, etc. Running a game in a desktop environment means that there are other session processes which the game needs to share resources with. We want to have a PlayStation like setup: game everything, everyone else nothing. I don’t want KWin to take away important CPU/GPU time from the game.”


    * Special case in Germany: professional Tax apps. All Linuxer I know still run a VM or a dual boot system with Windows for their Tax calculators. 🙂


  10. The context menu is not consistent. Some have one column (for icons or checkbox), others have two columns (one for icons and one for checkbox) and some have no columns. All of them producing a context menu of different sizes.


  11. What a huge pile of improvements. You guys are amazing, and I really mean it, because with such an small team, if you compare it to teams from other DEs from other OSes, you achieve great results beyond what would be expectable for a few people in their spare time. Congrats to all of you!

    Now, some criticism regarding the widget design:
    I’m a user of KDE since the 4.2 release and I’ve been always seeing how inefficiently do you take advantage of the screen’s space. Why do you waste so much screen area with empty grey areas? Why separator areas are so thick? Why Breeze seems like designed for touch screens with those title bars, buttons, text boxes, etc so thick that my finger could fit in?. And no matter if you try to tweak all of that in the preferences, the margin for tweaking is very narrow.

    Let me show an example using a screenshot from you:


    The first window, at the left, is one you have published in this post, the second one is a rapid mockup I’ve made optimizing the space and keeping all the widget’s elements intact (excepting the sliders’ width) and organizing the buttons in two rows (seriously, guys, rows and columns are nice, are your friends. Organizing elements and texts in columns/rows the space is hugely optimized). And the third one is another mockup, like the former but with the only different that buttons are in “icon only” mode. Something that doesn’t exist in Plasma for buttons in widgets but it does for toolbar buttons. I don’t understand why, because in case the user gets confused, a nice tooltip, like we have for the toolbars, and also an icon design in colors, would remedy it.

    You guys and Plasma are awesome, I never get tired of saying it, but not perfect, heheh. Please stop wasting so much square centimeters of our screens with empty grey areas that are totally useless. Most of us don’t have 32″ 4k monitors. Our poor little laptops will be eternally grateful to you. xD


    1. Yeah, sorry. I thought that pasting the diect URL would only show a link, and inserting the embedding code would show the image, but it turns out it’s more or less the opposite.
      I’ve posted it right now.


    2. Yeah, sorry. I thought that pasting the diect URL would only show a link, and inserting the embedding code would show the image, but it turns out it’s more or less the opposite.
      I’ve correctly posted it now.


    3. If you make the window smaller, it will pretty close to the second and third images with the exception that the buttons on the bottom won’t re-layout themselves or lose their text, and the comboboxes and tabs won’t get a little bit smaller like you’re drawn them. I don’t really see the big deal about those 4 pixels though. In general larger click areas result in faster user interfaces.

      There could be less padding around the tab frame though, that’s true. The fact that the tab bar frame doesn’t vertically align with the buttons is just a bug plain and simple. And I like the idea of having the buttons on the bottom lose their text when there isn’t room to display it. That’s something we should hopefully get automatically once we port System Settings and KCMShell (the app that renders standalone settings windows) to use a Kirigami toolbar, since Kirigami toolbars are responsive in that way.


    4. Well, that was a rough and quick mockup to explain the idea. Of course it should be rethinked and refined by the visual design team.

      The deal with those 4 px saved is that if you sum 4 px here, other 4 there, and then 6 – 8 in over there and there the total space saving begins to be noticeable, allowing you to have two or more windows on the screen without overlapping too much and disturbing each other, hence the user’s workflow.
      Also I don’t only mean applying those optimizations to dialog and configuration windows only, but a general optimization for Plasma’s interfaces which uses the screen to show more info and interactive elements and less empty areas which, besides, imply more mouse movement (a bit annoying when using touchpads).
      If you use to split your screen to have a window at its left and another one at its right, something very useful to drag and drop from, say, Dolphin to Kmail’s composer, this “split” organization of the screen turns out a real time saving and workflow more agile. But due to the, in my opinion, unnecessarily big widgets in Plasma, which intefere with such desktop area organization many times I desist and go back to use the whole screen for the apps and lose time “Alt + Tabbing” and copying & pasting. And I’m talking about 15,4″ screens, I guess in 13 or 14″ laptops must be worse.

      Nice to read about those ezxpected improvements by Kirigami, I’m eager to see them, but as told before, I think not only System Settings should benefit from it but the whole Plasma desktop and KDE apps. Design should be functional at first and aesthetic in second place, IMO.
      I’d wish that more developers, especially some from the design team could read this and take it into consideration. I hope some of them visit your blog and read users’ comments.

      In any case, thanks for reading.


    5. My full-time dev machine is a laptop with a 13″ screen. I have a Unity-style left-side double-wide panel, and I constantly have two windows tiled side-by-side. Here is what my screen looks like right now:

      So I am pretty much living in ground zero for that! 🙂 However I experience almost no problems of the kind that you describe. Whenever I find myself wanting to un-tile or mazimize a window, it’s never because the UI widgets in KDE apps are too big; rather, it’s because a website or app has a defective user interface design that assumes the window will be maximized or otherwise consume a lot of horizontal space. A few pixels here and there don’t really compare to the impact of this assumption. So by far the more effective way to fix the problem is to make apps (and websites, but that’s another story) more friendly to being used in a taller-than-wide window size. At least that’s the way I see it. 🙂


Leave a comment

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s