Polishing Plasma 5.12

Igor Ljubuncic of Dedoimedo published his review of the Plasma 5.12 beta recently. As always, he’s very thorough, and points out out issues that keep Plasma from being A+ quality. A major part of our Usability and Productivity initiative is honestly acknowledging user feedback and criticism with humility instead of defensiveness or dismissal. That way, rather than engaging in pointless arguments, we can focus on fixing problems!

With our aggressive focus on user satisfaction, we read these kinds of reviews very carefully and take their comments seriously. I wanted to provide a look at all the issues that Igor raised in his review. I went through every issue and made sure that if it was a legitimate bug, it was tracked with a Bugzilla ticket. Many already were, but some weren’t, so I filed tickets for them. Here’s the full list, along with the bugs’ status and our plans for fixing them, where applicable:

Default bottom panel isn’t optimal for using a global menu: this is true, but since the global menu isn’t shown by default, I think it’s fair that if you’re going to use it, you’ll need to change the UI a bit. This is why Plasma is so customizable!

Global menu only works in certain programs (e.g. not in LibreOffice or Steamc): it’s unfortunately not something we can fix; this is up to the distros and app developers. Ubuntu’s former Unity global menu feature worked for all apps because Canonical patched the software they packaged to make it work.

Sidebar headers are too light: (KDE bug 384638). Not a bad design decision, but rather a a bug caused by the choice of implementation.

Slight RGB hinting font anti-aliasing not used by default, even though that’s the best setting: (KDE bug 389598). We may be able to change the defaults here to improve things for the majority of our users.

Default font size should be slightly larger with Noto Sans: a controversial proposal, but might be worth it. I plan on doing some side-by-side testing for this.

Get Hot New Stuff never seems to works right and is full of outdated content: unfortunately, this is true. It’s a major pain point for a lot of people that we’re aware of and planning to put some work into.

Dragging a URL from Firefox to an Icons-Only Task Manager doesn’t work: (KDE bug 389613). Worth mentioning that this mostly works with a regular task manager if you drag it to the region that holds app launchers, not the window list part.

Discover’s settings/sources page is confusing and exhibits poor usability: Mostly true for distros that have a lot of repos, but a legitimate criticism. We’re discussing this internally.

Discover doesn’t offer a way to install NVIDIA drivers or other similar things: Discover is an app store, not a driver manager or a package manager, but we’ll see if there’s any way we can improve this.

Dolphin should add Places panel entries for Documents, Download, Pictures, and Music: (KDE bug 389618). A simple enough change, though I think it may take some doing to avoid introducing duplicate entries for existing users.

Support for smartphones (especially iPhones) is spotty: A known issue. We’re working on it, slowly.

Copying files to samba shared resets their timestamps: (KDE bug 356651). I am actively working on producing a patch for this!

KIO doesn’t mount remote filesystems locally like GVFs does: (KDE bug 330192). A major architectural issue. We may need to organize a development sprint for it.

Also, Igor marked as broken a few things that actually do work, or are already fixed in the next versions of the software:

You can indeed add folders to Dolphin’s places panel with the context menu!

Support for hiding whole sections in Dolphin’s Places panel has already landed in master and should be released with Dolphin 18.04!

Konsole tab issues were actually caused by Qt; they changed the behavior of the tab widget and we needed to adapt to that change.

Dragging a URL from Firefox’s URL bar to the desktop does create a shortcut to that URL. However, we can improve the usability: (KDE bug 389600)

How you can help

These kinds of issues are major pain points that get brought up over and over again in Plasma reviews and internet discussions. Fixing them has a disproportionate PR impact and generates a stupendous amount of good will. If you’re a developer, please try to hit one of these bugs sometime in the coming days or weeks! it will make a huge difference. This is how we move toward making Plasma a no-brainer choice in the Linux world.

Post navigation

41 thoughts on “Polishing Plasma 5.12”

THIS is true love and commitment to KDE. You do a fantastic job!
This kind of articles should be regular in kde’s dot and blog to be more close to the common user. May encourage some of them to start contributing to the project because they will feel heard.

That’s something different. The GNOME 3 AppMenu is frankly pretty useless as all it has in most cases is items for Quit and Settings (though some apps expose a few more things, as you indicate). But this is talking about apps with actual menubars: File, Edit, View, etc. GNOME apps that still have those don’t export them in a way that makes them visible to the Global Menu widget, to my knowledge–though I would love to be wrong about this!

Most Gnome apps don’t have the ability to turn off CSD. So what are you saying? That because there is one unmaintained Gnome text editor where CSD is optional, nobody should even attempt to implement the GTK 3.22 AppMenu?

Oh, by the way, the article refers to the global menu, which does work properly. But if I remember correctly, there used to be another plasmoid to also have the window controls (open / minimize / close) on a panel and automatically get rid of a window decoration for maximized windows (in the plasma 4 days) I think that is not supported anymore ? But then you partly lose the benefit of the global menu, if you have to add a top panel and cannot get some space back by removing the decoration. I know I’m probably slightly off-topic !

I’ve only recently found this blog, but since doing so I’ve subscribed via RSS and have been following it. What you’re doing is very impressive, and it makes KDE seem very attractive to me. I love what you’re doing with user feedback, especially given the kind of things that are going on with certain other projects. It makes me want to become a KDE contributor myself!

The only KDE app (that I found) that remotely supports smooth/momentum scrolling is Discover, but smooth scrolling does not work until the scroll bar is manually dragged to a new location (i.e. select the Applications category in Discover, perform a hover scroll from the top of the list and notice scrolling is painfully slow. Drag scrollbar to a new location and immediately hover scroll and scroll speeds are much improved). Aside from capping the maximum scrolling speed, Discover’s hover scrolling is pretty close to my preferences when it works.

I would like to see System Setting ->Mouse-> Scroll wheel options (similar to chromium smooth wheel scroller) for system wide momentum/acceleration hover scrolling that works for all apps including Dolphin, Kate, Widgets (Menu), Okular, etc.

Scrolling is a complicated beast, exacerbated by imprecise terminology. Here are the terms I try to use to keep the issues clear:

“Smooth scrolling”: animated transitions between scroll states when using a mouse wheel. Depending on the toolkit, this can be automatic, or manual. For example in Kirigami, I believe apps get this for free. I *think* the same is true of Qt QWidgets but I’m not 100% sure..
“Pixel/pixel-by-pixel scrolling”: scrolling using a touchpad that allows you to scroll in individual pixel increments, rather than X number of lines at a time. Same as above: apps get this for free if they use standard toolkit scrollviews, but some apps (e.g Kate, Konsole) use their own widgets and therefore do not get this for free, and would need to implement it themselves.
“Momentum/inertial scrolling”: when the view continues to scroll for a bit even after your fingers have left the mouse wheel/touchpad. Prior to libinput, this could be imposed by the input driver by sending fake scroll events after actual scrolling ended, so it could work everywhere, albeit with some unsolvable bugs. With libinput, it’s all up to the GUI toolkit’s scrollview to support it, and for the app in question to turn on that feature.
“Scroll acceleration”: when the mouse wheel scrolls by a small number of rows when you turn it slowly, but each tick scrolls by a larger number of rows as you turn it faster. This is 100% up to the input driver. Here’s the request to add it to libinput: https://bugs.freedesktop.org/show_bug.cgi?id=101141

it seems the mentioned bug is “KIO doesn’t mount remote filesystems locally like GVFs does: (KDE bug 389571). A major architectural issue. We may need to organize a development sprint for it.” is wrong

To restore the default settings on my openSUSE, simply go to the system settings – look and check to use the layout of the theme. This to me restores the default settings, I apologize for my English but I hope you understand the concept. Hello

You should become the new PR manager for the Plasma project and KDE as a community. I am sure there are many people out there who would like to know whats going on with KDE on what for bugs of features the devs are working ob but nobody writes about it. I enjoyed the few blog posts from Kai Uwe in the past but unfortunately the last post was quite some time ago and now you jump in this gap and fill it out completely. I enjoy every of your posts and to be honest before you started your blog posts I was even thinking about something similar because I am searching Google+, KDE planet, Phab and Reddit every day to get all new features and bugfixes (and wanted to have a counter pole against “World of GNOME” ) 🙂 GNOME gets so much attention and I believe that KDE and Plasma deserve some as well but until now nobody cares except for critism what made me very sad because I really like to work with Plasma every day I use it. It’s very good that you started your work, you help the project a lot with this, please keep it up.

Thanks for the encouragement! The FOSS world is a do-ocracy, and that’s more or less my goal–but also in a more overarching and technical sense too. I still submit a lot of patches. “KDE Release Manager” seems like a nice job title. 🙂

I am impressed. Usability is very important. I do not know if it is good or bad, I try to interest you in my major usability bugs:
– reading mails in unread mode instantly disappears from list -> https://bugs.kde.org/show_bug.cgi?id=259813 (made me switch to Thunderbird, which I really would like to stop using)
– [timeline] last month should show the files from the last 31 days (and further comments in the report) https://bugs.kde.org/show_bug.cgi?id=304892
– timeline syntax should be partly localised https://bugs.kde.org/show_bug.cgi?id=304762
– what I did not report yet, but commes to mind now that the timelinestuff, including the desktop search is missing in kde file open dialogue.

If you can confirm that https://bugs.kde.org/show_bug.cgi?id=304892 is still an issue today, then yes, please go ahead and re-open it with a (polite!) comment to that effect. I was going to investigate tonight, but feel free to beat me to it!

Getting attention on these bugs is definitely the first step, but as you’ve no doubt notices, we’re very under-resourced. Helping to recruit more developers is probably the most important thing you can do to help right now, if you’re not up for programming yourself.

Hi, nice to see a response that takes software critique seriously.
I have discovered a bug that is present both in 5.8.8 and 5.11.95, this one: https://bugs.kde.org/show_bug.cgi?id=349673 What I’m wondering is, how do I mark this as affecting Plasma 5.11.95? Is is sufficient to leave a comment (which I already did)? And yes, I’m new to KDE bugtracking.

“Discover doesn’t offer a way to install NVIDIA drivers or other similar things: Discover is an app store, not a driver manager or a package manager, but we’ll see if there’s any way we can improve this.”

An Idea: Put a button that opens the already existing system settings menu to install NVIDIA drivers, and another button that opens the installed package manager or in case there isn’t one installed, that leads to suggested package managers to install. I don’t know if that is already done or if not if it’s possible, but would be a nice intermediate solution.

That could work. We’re currently discussing a more general solution: adding another backend that handles drivers. This would help distros out too, since they wouldn’t each need to write their own driver manager apps.