Are you sure it's not a you problem? Or isn't it a you problem? Go read the docs.
Have you contacted the devs? Reporting a bug would be helpful.
Sorry to be so rude, but you really hit a nerve. It isn't even your fault.
Anyway, rant time:
KDE and bug reports. They always come to you like "Hey, bug reports are so really importsnt to us! And we'll guide you through it. Here's our lovely oh-so-helpful wizard!
Except it ain't lovely. Nor helpful. The only thing it does is pop up whenever a KDE app has an aneurysm and asks you for a backtrace. And then... backtrace is declsred useless.
Why even bother people with the stupid popup if in 90% of cases it's declared as useless. Why not do the backtrace silently and then annoy the user only once you declare the bug "useful".
Last instance of this: I was using my KDE desktop. For some reason, Plasma seems to really hate me, because I need to fix default apps every few weeks. For some reason, jpegs and pngs open in Krita by default.
So, wanting to close Krita, becuse I don't need an entire editor to look at a photo, with tools taking up 25% of the screen, when it asked me about the import resolution, I pressed 0. Krita proceeded to crash and open the report bug dialog.
Not having seen the KDE report wizard for quite some time, I felt inclined to go fill out the report. Got through the first few pages just fine. Then came the backtrace. Sure, do it. I'd like whoever debugs this not snooping through a data dump containing god knows what, but sure. Then it gets called useless. AFTER you've taken 30-ish seconds of my life on preliminary questions.
Look, if you're gonna ask people for input and discard said input if something unrelated happens, at least ask after the something unrelated decided it's not gonna be yeeted away. No need for the "Oh, wait, we don't really need this, it'll take too much time to play detective" after the user already passed three screens of interrogation.
Anyway, the point is:
KDE clearly doesn't care about bug reports. Because if they did, the guide on installing backtrace-enabled packages once the inevitable verdict of "useless" wouldn't be a wiki page with the generaal message of "find backtrace-enabled packages, you buffoon" when you could point to them.
Another problem with this is: when a bug happens without backtraceable packages, how is the user supposed to recreate it if they don't know how?
And besides, my bug is very recreateable. Open an image in Krita (preferably from Dolphin, after Plasma mangled the defaults, again and again). When prompted for some integer, enter "0". Instead of a generic error message, see the entire app sink into oblivion.
Anyway, if anyone feels like reporting the totally useless report with totally unrecreateable conditions, feel free. I won't. Just too much work, for it to be discarded just like that by some wizard no one even thought through.
And why would I contact the devs? Or rather, where could I do that? They're worse than government agencies, for god's sake. The right person or place just doesn't exist. Wherever you go to or ask, it's someone else's responsibility or your fault. And the wizard, that true single point of contact - refuses any contact just as consistently.
So tell people to call the devs. Tell them it's their fault. Tell them to make a bug report. Say it just might help not just you, but someone else when all hell will freeze over before anything like that becomes even a remote possibility.
Talk about adding insult to injury.