https://bugs.kde.org/show_bug.cgi?id=480800
felixbra...@quicknet.nl changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |felixbra...@quicknet.nl
--- Comment #18 from felixbra...@quicknet.nl ---
(In reply to Christopher J. Bottaro from comment #17)
> (In reply to Steven Mey from comment #16)
> > Another workaround is to change your hotkey to custom command:
> > /usr/bin/krunner --replace
>
> Thanks for this. It's a big sluggish running this way though. The status of
> the bug is "closed upstream" does that mean a fix won't be coming unless we
> convince someone upstream to care enough to look into it? I.e. krunner is
> just broken until then?
Looking at the KDE bug triaging process it does seem like that is the case
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#It's_a_bug,_but_not_a_KDE_bug_(i.e._UPSTREAM/DOWNSTREAM_issues)
There is a bug report over on QT's system
https://bugreports.qt.io/browse/QTBUG-131899?jql=text%20~%20%22qt.qpa.wayland%3A%20eglSwapBuffers%20failed%20with%200x300d%22
Similarly people have been reporting this issue to NVIDIA on their forum
https://forums.developer.nvidia.com/t/570-release-feedback-discussion/321956/90
Neither has seen any movement really.
This is a particularly nasty bug: non-deterministic, occurring in upstream QT
code, likely related to NVIDIA's closed-source driver. Since KDE applications
are affected by this (pretty badly since with the 570 driver) I would say it is
in their interest to start working with QT and/or NVIDIA for a fix. I am
however an outsider to the KDE project and I do not presume to dictate what
they should and should not do.
--
You are receiving this mail because:
You are watching all bug changes.
