https://bugs.kde.org/show_bug.cgi?id=485770
--- Comment #4 from pallaswept <pallasw...@proton.me> --- (In reply to Christoph Cullmann from comment #3) > Hi, that is outside of our hands, if that needs to be improved, one must > report that upstream to Qt. Thanks for looking at this for us Christoph! I had a feeling that this might be upstream, as this issue appears to effect various apps, eg https://bugs.kde.org/show_bug.cgi?id=468794 I took a look at Qt's bug reporting, but they ask for a lot of info that's a bit above my capacity as an end-user. I am really not tooled to give them things like example code to reproduce. They're pretty clear that the quality (or lack thereof) that I could provide would result in a low likelihood of a fix. I wonder if maybe a KDE dev might be able to push this upstream? I'll do whatever I can as far as user testing goes. I'm keen to help out (obviously, I'm here!) but I think I'd do more harm than good by being the one to raise this to Qt. -- You are receiving this mail because: You are watching all bug changes.
