This week in KDE: bug squashing and more

This week we continued fixing bugs in Plasma 5.17! We know that it was a bit buggier than the 5.16 release was, and we strive to do better. If you’d like to help out with this, please test our Plasma beta releases by switching to the unstable/beta testing repos in your rolling release distro of choice. For example, Arch and openSUSE Tumbleweed. Beta releases of KDE apps will show up in these repos as well. It’s super fun! Try it, you’ll like it! 🙂

New Features

Bugfixes & Performance Improvements

User Interface Improvements

How You Can Help

I mentioned testing Beta releases earlier, but here’s something else! Do you like the idea of running a KDE-endowed free software operating system on your phone? I know I do. But did you know that KDE already has a mobile platform called Plasma Mobile? It’s real and it works and it needs your help to become mainstream! If this sounds like your cup of tea, check out https://www.plasma-mobile.org/findyourway/. You can read the Plasma Mobile project’s weekly updates in a format similar to this one here: https://www.plasma-mobile.org/blog/

More generally, have a look at https://community.kde.org/Get_Involved and find out more ways to help 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!

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

17 thoughts on “This week in KDE: bug squashing and more

  1. I experienced no bugs personally. After a year or so away I came back and was shocked at how stable and bug-free it’s been for me on Manjaro. I used to need to go into nvidia settings to fix screen tearing, but no longer! Amazing work by the KDE team. thank you for such a light and customizable desktop and apps.

    Like

    1. Yeah, there are many use cases where the whole experience is largely bug-free. However Plasma is so featureful that people keep finding bugs in the less commonly used features. 🙂

      Like

  2. Some nice improvements this week.

    The Plasma 5.17 regression with a multiple-monitor setup that is not recognizing unplugging event is hanging and not given much of an attention:

    https://bugs.kde.org/show_bug.cgi?id=413174

    So far some users and Nate got interested in it but no developer who can do something about it spoke up. So the issue is hanging till the proper persons will look at it.

    Like

  3. Dolphin telling what’s blocking the unmount of a volume is nice, but I would show it as:
    One or more files on this device are opened in the Image Viewer (gwenview).
    I think it’s more user friendly to show the generic name first and then the more precise one.
    Also seeing image viewer or video / media player is easier to remember which file you left open (a picture or a movie).

    Clicking on the volume indicator icon to mute that audio source like in Firefox is very cool, I remember that I tried this in the past. I’m glad that now it works.

    As for bugs, I see that going to the right side of the screen where the scroll bar is and then clicking and holding and dragging the mouse up or down doesn’t scroll the page in Firefox as it does in dolphin.
    I saw it at some point working, but now it’s not working again.
    I’m not sure if the problem comes from Firefox update or Plasma update.

    Like

    1. Rather than missing a generic name, I would say the problem with Dolphin’s new error message is that you don’t know what Dolphin was attempting to do.

      The current error message is like:
      ‘The device is currently busy: Error unmounting /dev/sdc2: target is busy’

      So instead of:
      ‘One or more files in this device are opened in application “okular”‘

      The following would be more descriptive:
      ‘Error unmounting /dev/sdc2: one or more files in this device are opened in application “okular”‘

      Like

      1. +1

        Question: If there are more blockers, does not Dolphin list them as well?
        How about adding a button to attempt to close the blockers like Windows does?

        Like

  4. I think it would be helpful to include a button asking if you want to proceed with device removal even with open programs.

    If you are viewing a photo in gwenview and decide to remove it, this will not cause any problems.

    Like

  5. It would be handy to be able to drag and drop multiple desktop files at once into kmenuedit. When there are a few to move you have to do it one at a time. Also every desktop file has “-2” added at the end of its title. Why is that?

    Like

Leave a comment

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

WordPress.com Logo

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

Google photo

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

Twitter picture

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

Facebook photo

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

Connecting to %s