See what I mean? This has been a familiar pattern on their bug reports.
They try to fix things…
They end up breaking other things…
They’re not sure how they messed up…
They try to justify their decision…
They stall, stall, stall, procrastinate, etc, etc, etc, and the bugs just remain for years.
They’ll tell you it’s not a bug. Then it is a bug. Then they give you some esoteric reason why it cannot be fixed without redoing KDE from scratch by finding a cure for cancer with a rare floral ingredient found only in the deepest tropical jungles that blooms one day each year just before the sun sets, and blah, blah, blah.
I’ve had conversations with a few other KDE users over email (bumping into each other through bug report comments), and they share the same sentiment: there’s no point in filing bug reports against KDE because of the constant foot-dragging and developers’ not being forthcoming about real issues.
It’s like a running joke at this point.
I’m sure others have better luck and experience, but it’s been a frustrating experience for me.
Derrick: Here’s a bug. Here’s my system info. Here’s a video of it. Here’s how to reproduce it. Here’s some additional info.
Nate (KDE): This is by design. Our users love it! I’m sure you’ll end up loving it too.
Derrick: It’s a bug. It makes no sense. It shouldn’t be doing this, this, and this.
(months later)
Sarah: Wow! I got the same issue! Here’s my info.
Nate (KDE): I must consult with my other developers to figure out if this really is a bug.
Nate (KDE): Okay, it’s a bug. But it’s really confusing. Looks like something broke when we tried to create a fancy new feature that our “users” supposedly requested some time ago. (Trust me, bro.) We’ll have to figure out a way to fix it, I guess.
(three years later)
Derrick: Is anyone even trying to address this bug?
(crickets)