Plasma – The road to perfection is paved with bugs

Call it bias, call it taste, I like the Plasma desktop environment. After many years, I feel KDE is finally regaining some of that solid pro feel it used to have back in the (g)olden days. But then, the feeling of satisfaction is not guaranteed. Quality is a fickle thing in the Linux world, and KDE is not immune to regressions, especially when compounded by distro permutations and hardware dependencies.

Now, one might claim that a great operating system – and a great desktop – are immune to tiny variations in the operation setup. I agree. And so, I’d like to compile a list – with the necessary discussion of course – of some (of the many) things that I currently think are missing in Plasma. Things that could and should and would make it a professional contestant in the desktop world, currently a VIP club mostly reserved to Microsoft and a few other members. Then, some of you have expressed a view that I’m too biased when it comes to Plasma, but the lack of criticism (perceived as such) comes from the fact that Plasma is actually a genuinely good desktop environment. But it’s not perfect. Not yet. And here’s why.


So before we begin. Just a few quick notes. Most of the stuff comes from day-to-day testing, usually over a period of (just) several hours. My observations follow a simple usage logic, from initial connectivity to fun stuff that people need. Legend wise, [C] denotes cosmetic and [F] denotes functional. We talked about a lot of this stuff in my State of Plasma article from early 2017 and more recently the 5.12 LTS review.

Most importantly, this is not any kind of replacement for official bugzillas or an attempt to ape them poorly and with much less detail. This is more of a running, on-the-go impression from a user with a keen sense of OCD and aesthetics, and a simple approach to computing. Things should work. They should be intuitive, robust, elegant. Regressions are horrible. Stability and quality are the factors that determine success in the long run.

BTW, most of the stuff I have mentioned in the 5.12 LTS review are getting attention and focus by the KDE team. These guys are taking the problem seriously, but as most things Linux-based, their approach is from the dev perspective, mine is strictly from the user perspective. In fact, there’s extra work being done on ironing bugs, and this in turns is drawing more and more people to join the Plasma community.

The (short) list

Brace yourselves, here we go. And so I was merrily journeying across the Plasma desktop, when …

[C] Widget button on the left side is too close to the desktop folders.

[C] Widgets list always opens on the left side, regardless of the button placement.

[C] Wireless icon (when not connected) is too pale and may be mistaken for a gap in the system area in the panel.

[C] When connecting to a Wireless network, the user may be prompted for password twice, which is probably related to the KDEWallet service.

[F] When you add/pin applications to the task manager, the menu auto-closes. This is annoying and distracting if you want to add more than one icon at a time.

[F] Menu session end buttons all have the same result, regardless of what you click on. Whether you choose suspend, reboot or shutdown, you still have a 30-sec timeout screen with the same options presented again. A confirmation is nice, but it should also correlate to the chosen action. Clicking suspend or reboot and then choosing shutdown a few seconds later negates the first choice.

[C] The system menu does not differentiate between several versions of the same application, if installed. For example, the standard repo and the snap version of VLC 3.0 both show exactly the same, and the only way to tell them apart is by the icon (lower-res for the snap), or alternatively, by launching the program to check which version it is.

Plasma menu, multiple entries

[F] The order of different versions of the same application as listed in the system menu changes based on usage/launches.

[C] Panel height resize is done using a drag/slider rather than a precise input value. Both options ought to exist, so that both methods can be used. Hand sliding, especially without an external mouse pointer, is tedious and inaccurate.

[C] Brightness slider does not go all the way to the right on the 100% mark.

Brightness slider

[C] The clipboard in the system area, after you copy media files, does not have a perfect vertical alignment, leading to the bottom-most line to be partially obscured (cropped).

Clipboard line crop

[F] Default font color is too pale – insufficient contrast; should be black.

[F] Default font size is too small (10pt).

[C] Default font anti-aliasing settings are sub-optimal in all tests I have performed, including different laptops, with Intel and Nvidia graphics. The system defaults should be set to RGB and slight hinting.

[F] Spectacle does not have an option to remove/disable shadows when taking a screenshot of an active window area. The shadow size also depends on the selected theme – and may be impacted by compositing, which can lead to inconsistent results. It is also not apparent whether there are shadows in created screenshots or not while they are being taken.

[F] Spectacle usage model is complicated – Save & Exit is the same button that opens the preferences menu, and it is not immediately apparent this is the case. It also makes no sense to place the two under the same hierarchy element.

[C] System settings menu opens at a “wrong” default size, leading to category labels text breaking over multiple lines.

[C] System settings category labels are too pale – and barely visible.

[F] The installation of new themes, icons and other decoration is vague and broken. Sometimes, there are multiple install options that do not clearly signify to the user what they’re installing, and these installations often fail due to misconfigured third-party resources. Even when installed, decorations may not show up in relevant lists due to unlisted incompatibilities. It may take a full session restart (log out, log in) to see the effects of newly applied decorations.

[F] System customization should include a backup and restore-to-defaults options, including a desktop/system wide configuration, as well as individual options. This may also be realized as preview function, so the users can see what the new theme/decoration will do before it is applied.

[F] Discover shows no screenshots and no rating for selected programs.

[F] Discover sources management remains confusing and insufficient – no way to change locality/priority of listed distributions, no way to search or install proprietary software.

[F] In the sources view, Discover has a scrollbar that obscures the list of repos and also partially blocks the UI itself.

[F] Discover seemingly keeps on checking for updates, even though the action is not happening and/or it should have completed already.

[F] Discover search results are broken; programs that can be found using the command-line package manager utility do not show in the UI when the same search string is used.

[F] It is difficult to find the option to configure/enable the desktop session restart (X kill), normally activated by the Ctrl + Alt + Backspace combo. There are no less than three different options to configure and use keyboard shortcuts. You have normal and advanced settings, but then you also have the hardware configuration, and it’s the last one that you actually need for this.

Desktop restart key combo

[C] Dolphin requires drag ‘n’ drop to add shortcuts to the sidebar; an (easily discoverable) menu option would be preferable, especially for network shares.

[C] There’s no easy way to quickly remove/hide entries in the Dolphin sidebar, except by removing the entire category.

[C] The list of devices in Dolphin seems random – devices should include both label, device name and size through a configurable setting, and there should be an option to allow the user to sort the devices based on their preference.

[F] In Dolphin, copying files to Samba shares will result in their timestamp being updated to the current mark. This is most significant when working with pictures.

[C] No way to add multiple versions of same application as separate (custom) launchers to the task manager. This is only possible via configuration file tweaks, with session logout to take effect, and even then, launched programs still default to the original (pinned) application launched.

[C] No way to add URL shortcuts by drag ‘n’ drop from browsers; no favicons are used as shortcut icons.

[C] No way to add an existing URL shortcut (on the desktop) to the task manager. Launched program/site via the shortcut defaults to the browser application icon.

[C] The panel clock is too big – full height – while the rest of the system area icons are smaller. The use of the alternative gadget Event Calendar helps, but this should be a customizable option in Plasma defaults.

Plasma clock

[F] KDE Connect only works with Android devices.

[F] iPhone/iOS devices will not be auto-mounted in Dolphin; you may need to use a manual configuration to identify and mount them.

[F] The mount prompt in the system area (regardless of the device/phone/camera) type is vague. It offers several mount options, associated with programs, but it does not identify the mount protocol, e.g. MTP or PTP. This only becomes apparent after the device has been mounted and presented in the file manager.

[F] There is no umount option for phones or cameras in Dolphin.

[F] Media playback (music and video) from Samba shares does not work well. There is no unified approach to how the remote filesystems should be treated, and it is up to individual applications to handle authentication and playback.

[C] Not all media players have system integration, and/or some have their individual icons + media playback button in the system area.

[F] Accessibility options are vaguely defined or executed. They should be available out of the box and configured for immediate use, including the lock and login screens.

Orca missing

[F] Open file dialogs for different applications behave in different ways, including how directory trees and files are displayed. Often, paths and names are truncated, and there’s no standard display method.

And thus ended a short session of use. A single one. Imagine what happens if 100 people did this daily.


There you go. Now, before you say “But Windows or Gnome also …” Wait. Stop. The purpose of this list is not to seek solace in failures or incomplete/imperfect implementations of desktop environment solutions that may exist out there. The purpose is to express my view, as an individual user, of the big and little things that do not seem to work well in Plasma. After all, the desktop is there to allow people to enjoy themselves, to have fun, to be productive, and whatnot. And every little papercut or inconsistency is detrimental to the experience.

It would be a nice exercise to actually do the same thing with … other desktop environments. I believe that Plasma probably has the fewest issues, as odd as it may sound after you’ve just consumed this long j’accuse list. But it is still not perfect, it’s still not good enough to everyday use, and there are many things that need to be improved. Then again, no one said creating a splendid desktop environment was going to be easy or boring, right. Take care, and perhaps in your comments, you will come up with a few more niggles that I missed. Let’s hear your thoughts. Spill them out.



Cover image courtesy of (CC BY-SA 3.0 Unported).


43 thoughts on “Plasma – The road to perfection is paved with bugs

  1. There’s more for KDE to be perfect:
    – true secure removal of external hard disk (must be turned off after eject is chosen).
    – print options for okular were reduced. Now, we can’t choose if we want to print on portrait or landscape, the size of picture and its position on paper.
    – kate has a bug: copy a long text from Firefox and paste it in Kate = don’t work
    ps: all the facts above works alright at gtk.

    • “true secure removal of external hard disk (must be turned off after eject is chosen).”
      I was about to suggest this myself. Currently, I use Gnome Disks to power off my external HDD. Should be available from the device widget (and please don’t reply with a terminal command for this, I will NEVER remember it ;P).

  2. Also:

    [F] In the font config tool, allow the user to increase/decrease font sizes by 0.5 numbers.

    [C] Promote the Activities feature more, perhaps in Kicker (as a link or shortcut). Why: Because I think many users miss out on this useful feature; I only discovered it by reading about it on this website, for instance.

    [F] Make Power Settings per activity also configurable from the Activities main view (I mean the view from Desktop right click ? Activities ? Settings). For unified settings access.

    [C] Decrease width of Discover’s sidebar by at least 25%.

    [C] The large category images look nice, but they take up too much space (Discover).

    [C] Rename “Settings” to “Sources” or something similar (Discover)

  3. [C] Default font anti-aliasing settings are sub-optimal in all tests I have performed, including different laptops, with Intel and Nvidia graphics. The system defaults should be set to RGB and slight hinting.

    Totally agree.

    [F] Default font size is too small (10pt).

    Personal taste. 10pt is perfect for me. 11pt is to big IMHO. For example in Ubuntu/Gnome fonts are way too big for my taste.

          • Nope. Done too much work for KDE in the past with no results. Leaving the bug reporting to those using it day-to-day. I just check it out every year or so, to see if things finally work well enough to consider installing it. Not yet. Cinnamon is still the best for my new installs/ Linux converts.

          • I understand. Linux Mint is amazing. Unfortunately, it’s built on rotting foundations, which is why I’m with KDE instead of them. KDE Plasma’s long-term outlook is much sunnier, if we can manage to gain their laser-like focus on the out-of-the-box user experience.

          • I am not a developer and I love Plasma. I am also a fan of Linux Mint and I was wondering if you could elaborate on Mint being built on rotting foundations? I am curious to both know and understand. Thank you.

  4. They should start to think about ways to make money to support development, because nothing in the world is free. If something is free, means, someone has already paid for that.

  5. Very true.
    I am huge fan & supporter of KDE, but could not stand longer that buggy Ubuntu 16.04 + KDE mixture (Kubuntu+LTS, Neon+LTS atc., starting from unbootable USB sticks, crashes during installation, ending with Dolphin and Control Panel crashes after fresh install – it is so frustrating!!!!) and switched back to Mint after many years.
    I was told once in support forum “What do you expect?! It is a free software!” 🙂 maybe it is enough already? 😀

  6. BTW, some of the stuff I mentioned are definitely fresh bugs and/or regressions. The volume slider manifests in KDE neon stable dev build with latest 5.12 (about a week ago), with the standard Breeze system theme (light) with dark desktop theme (basically menu and panel).

    Re: Dolphin, right-click for bookmarks is nice but it is not functionally equal to actions that are available through the menu or toolbars, at least no from the UI flow perspective.

    There are a few others points, but they were no casually brought up – all of that is relevant/current with what the neon repos reflect from a few days ago. Of course, I’m more than looking forward to improvements and fixes. There will be those kind of articles, too!


  7. If not everyone would try to create a new distro there would be enough development resources. But so long a “me too” developer “ego” seems to be more important than product maturity and user satisfaction Linux desktops will continue to suffer from poor quality. If we would have 10 distros and not hundreds then chances to develop a great desktop would be much higher.

  8. “Things should work. They should be intuitive, robust, elegant. Regressions are horrible. Stability and quality are the factors that determine success in the long run.”
    I keep that.

  9. So you don’t even mention broken multi-screen modes ?

    Such stuff is much more serious than the mentioned details and it is taking the desktop experience 10 years back.

    • One, can you elaborate more. Two, I don’t mention multi-screen modes because I don’t use multi-screen setups. I find them unnecessary and ergonomically bad. They might serve a purpose for people who need constant logs/terminals in addition to something else – arguable, as it is still a fairly inefficient way of doing things – and that’s not 99.9% of users.

      • I refer to the fact that KDE is unable to preserve window positions while you plug an external monitor.
        It leads to ridiculous situations when you are in front of an audience.

        See :

        Gnome, Elementary, and of course Windows / Mac OS all handle it properly : you plug a new monitor, and your windows stay where they are (and especially, they don’t show up on the newly plugged monitor).

        I disagree with you regarding the ergonomics, but that is another topic and it is very subjective, so no problem.

        But you have to recognize the huge need for multiscreen for a majority of professional users (meetings, reports, presentations) and ALL trainers or teachers.

        You mentioned KDE as a potential professional contender.

        But without proper multi-screen management, it is going to remain a nice toy for home, but not seriously usable in a corporate environment.

        • You are right in that there are certain other requirements for corporate environment. Work environment requires even more than the home setup. That’s the next step. Beforehand, I think, KDE should nail the home usage formula first.

  10. “Call it bias, call it taste…After many years, I feel KDE is finally regaining some of that solid pro feel it used to have back in the (g)olden days…”

    “Bias” is a very good descriptor.
    Based on the combination of the aura of stasis surrounding KDE progress, and poor design decisions, “bias” is the only descriptor.

    Precisely how many more years will you give KDE to return to its “…solid pro feel it used to have…”?

    • I don’t know. So let’s set a deadline. Say 2020. If it does not happen by then, what then? Delete Linux? Because from that perspective, I might not as well bother at all and just use Windows. No one is born a champion. But the journey to become one is what separates winners from losers.

      • Well, Arch is always available. Linux itself is pretty functional, and KDE gripes are not going to make me delete it outright, although right now I’m messing with the framebuffer myself, so I’m not even using KDE software and might not understand your trouble.

      • Windows may be king of the hill but it has its fair sure of bugs. It may not suffer from the regression bug that keeps biting Linux but that does not mean desktop Linux has not continually improved. I think it has gotten to the point of taking three steps forward before taking that one back.

        MX-Linux, Linux Mint, Deepin 15.x and KDE Neon are very usable and have fairly minimal regression happening lately. OpenSUSE Argon has been another surprisingly smooth ride. I have settled on these as my daily drivers and they have served me pretty well for over a year now. That in itself is a big improvement from prior years when a great distro received an update that rendered it garbage, more often than not.

  11. Igor, while you’re here, let me ask you something. People over OMGUBUNTU have been throwing comments on your reviews by criticizing you don’t have a comments section on your own website. Also they argue that you test Linux distros on top of old hardware. Can you address this? Thanks.

    • Criticism is a necessary part of communication exchange among people with different views, abilities and experiences. If someone doesn’t like what I do, well, no biggie.

      • I am sorry. I meant for you to address those concerns more specifically: why does your website doesn’t have a comments sections like in here, example? Can you justify, even with the worst / selfish / sovereign argument? You don’t have a comments section there, why? About using old hardware, is it because you like testing that way for whatever reason? I actually never noticed the said “ancient hardware” in your tests, but now that someone brought that up, I’d think you could explain why as well? Anyways, one way or the other I find your website and books excellent. But it would be help me to understand if you answer this in a more straight forward manner.

        • Justify? I don’t need to justify anything to anyone. Do email me please, and I’ll explain if you want, there’s no reason to pollute this article with my personal antics.

          • Don’t worry, I get it. I can think of the reasons why I myself wouldn’t want a comments section on my own website if i had one. There would be certainly some folks there to bash just about anything and never happy (as I see in OMG Ubuntu site) and a huge amount of trolls. About the hardware thing, I also may have the same thoughts – I don’t buy computers to replace them each 3 years. My machines are chosen to last for at least 7 to 10 – but that is not how the industry really works, they want you buying something new every other day. These things need no explaining really.

  12. another regression,, dolphin. It used to work
    A zipped html, for example a baen ebook, you cannot follow the links
    (view archive as folder) opens the zip in SEVERAL subdir
    under ~/.cache/kioexec/krun/ ,, so the links don’t work
    In the past, it all just worked

  13. It would appear Plasma’s developers are visiting your posts. You always nail it with regard to what could use improvement. I have used Plasma for so long I miss a lot of the little issues you always find. Once I become aware of them I can no no longer overlook them. In fact, they begin to really bother me.

    Regressions really have no place and should not even keep cropping up. Many, have finally started to see some developer attention. Regressions have become a ‘normal’ issue for those of us using desktop Linux that it is viewed as just part of the deal. What can be done to eliminate the problem remains elusive and it does not help that developers do not approach the issue from a users perspective.

    I wish you could be an official advisor because desktop Linux would be much better for it. You nail it on every desktop environment you target. Keep up the great work!

  14. Error thrown

    Call to undefined function echo_views()