Please report a bug rather than creating a task here for every small glitch/bug.

That would be the ideal thing to do, agreed. On the other hand, it would take ages and I'm highly skeptical the issue would be addressed.

I assume this bug is also present on your machine, is it not?

I'm not the easiest person to put up with, agreed.

In T8607#139990, @raddison wrote:

Please report a bug rather than creating a task here for every small glitch/bug.

That would be the ideal thing to do, agreed. On the other hand, it would take ages and I'm highly skeptical the issue would be addressed.

You would be wrong. KDE bugs are actively triaged--especially bugs to plasmashell (and this is a plasmashell bug). Kubuntu mostly consumes software that KDE produces; patching at the Kubuntu (distro) level is rare and undesirable compared to getting the fix pushed out to all KDE users across all platforms. It's not feasible or desirable for Kubuntu to fix every KDE issue you find. For the most part the best we can do is cherry-pick a patch that the KDE people produce, but that patch won't ever get produced unless you report the bug to them.

I'm not the easiest person to put up with, agreed.

A wise man can admit his faults. An even wiser man learns how to change.

:) Okay,

Please report a bug rather than creating a task here for every small glitch/bug

@rikmills @ngraham I'm quite impulsive by nature. I'm sorry I've started with the left. The bug seems to be present on most (if not all) machines and it has not yet been fixed. Seems to affect Kubuntu exclusively. (I can see it even in Tunnell's promo video). Where exactly should I report it to? To https://bugs.kde.org/ or Launchpad?

Too late, somebody else already filed it: https://bugs.kde.org/show_bug.cgi?id=395618

Too late, somebody else already filed it: https://bugs.kde.org/show_bug.cgi?id=395618

Okay then. Hopefully, it'll be fixed. Thank you, Nathan.

Okay, seems this is the only way to get rid of the glitch.

Just choose "None". But you already know that, don't you?

Reboot might be required to take effect.

T7618 Probably the root of the issue.

Please report a bug rather than creating a task here for every small glitch/bug. That way, should anyone else happen to be experience the same, they can find it in bug reports, confirm and give more info.

@rikmills It's been done. Something must have gone wrong when upstream settings have been changed in Kubuntu. What do you think?

A good example of why you should be cautious when changing upstream settings.

It's an upstream bug, and it would have to be fixed there anyway. In fact, the fact that Slight RGB font hinting is not the default setting upstream is itself a bug, so once upstream fixed that bug, Kubuntu would have experienced the issue in question anyway regardless of whether or not we made this change ourselves.

In short, your last comment was irrelevant and pointless, and I would urge you to stop spreading FUD or I will have to ask you to leave.

It was a upstream bug indeed. Which should have been sorted out before and not after altering the defaults. So the order was all wrong.

Nobody knew about the upstream bug until we were actually using the new setting. That's how bugs get found.

It should have been obvious as soon as the defaults were changed. That way upstream could have been engaged earlier or the altering couldn't have been delayed. It was an unfortunate happening. All I'm saying is that maybe we can learn something from it. Lol, I'm not blaming anyone. It was OUR failure.