SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I cannot reproduce the start condition, but sometimes krunner does not open and each shortcut keypress leaves this log: Feb 03 16:44:52 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0dc9e70 Feb 03 16:44:52 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0dc9e70 Feb 03 16:44:53 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0dc9e70 Feb 03 16:44:53 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0dc9e70 Feb 03 16:44:53 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0dc9e70 Feb 03 16:44:54 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0dc9e70 // After some time, it returns on its own. And then it randomly stops, and again each keypress leaves something in the log: Feb 03 16:49:43 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0d676c0 Feb 03 16:49:52 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0d676c0 Feb 03 16:49:53 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0d676c0 Feb 03 16:49:54 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0d676c0 Feb 03 16:50:07 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0d676c0 Feb 03 16:50:07 arch krunner[4832]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x7ca8d0d676c0 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux arch 6.7.3-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 01 Feb 2024 10:30:25 +0000 x86_64 GNU/Linux (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Nvidia 545.29.06-3 ADDITIONAL INFORMATION - Did not happen in x11 - pkilling krunner makes it work again instantly
Additional info: this also happens in 5.27; although less frequently
The error code means EGL_BAD_SURFACE. I don't think this is a problem in KRunner, but might be in Qt or the NVidia driver. Please try to reproduce the issue with an older driver version, and if it happens there too, report it to Qt, if it doesn't, report it to NVidia.
*** Bug 491530 has been marked as a duplicate of this bug. ***
*** Bug 491380 has been marked as a duplicate of this bug. ***
I have created a workaround for those who are addicted to krunner, because I don't see there will be a patch soon. https://github.com/kpostekk/krunner-restarter
*** Bug 491483 has been marked as a duplicate of this bug. ***
*** Bug 495776 has been marked as a duplicate of this bug. ***
*** Bug 496248 has been marked as a duplicate of this bug. ***
Currently impacted by this issue, we are temporarily using a workaround script to monitor journal events and restart the service. Do you know when this bug will be fixed?
(In reply to rabin from comment #9) > Currently impacted by this issue, we are temporarily using a workaround > script to monitor journal events and restart the service. Do you know when > this bug will be fixed? Adding missing system info for context, ``` Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 Kernel Version: 6.11.11-300.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6820HQ CPU @ 2.70GHz Memory: 62.6 GiB of RAM Graphics Processor: Quadro M2000M/PCIe/SSE2 Manufacturer: LENOVO Product Name: 20EN001EUS System Version: ThinkPad P50 ```
(In reply to rabin from comment #9) > Currently impacted by this issue, we are temporarily using a workaround > script to monitor journal events and restart the service. Do you know when > this bug will be fixed? This will rely on someone creating a bug with either nvidia or Qt, as the problem is in one of those codebases. See this comment for context https://bugs.kde.org/show_bug.cgi?id=480800#c2 Since your system doesn't have an nVidia GPU, the problem is likely with Qt.
(In reply to TraceyC from comment #11) > (In reply to rabin from comment #9) > > Currently impacted by this issue, we are temporarily using a workaround > > script to monitor journal events and restart the service. Do you know when > > this bug will be fixed? > > This will rely on someone creating a bug with either nvidia or Qt, as the > problem is in one of those codebases. > > See this comment for context > https://bugs.kde.org/show_bug.cgi?id=480800#c2 > > Since your system doesn't have an nVidia GPU, the problem is likely with Qt. I do have an NVIDIA card (Graphics Processor: Quadro M2000M/PCIe/SSE2) So first I need to check if I can recreate this issue with older drivers?
Yes.
(In reply to rabin from comment #9) > Currently impacted by this issue, we are temporarily using a workaround > script to monitor journal events and restart the service. Do you know when > this bug will be fixed? The workaround script isn't there any longer.
(In reply to BlueUSA from comment #14) > (In reply to rabin from comment #9) > > Currently impacted by this issue, we are temporarily using a workaround > > script to monitor journal events and restart the service. Do you know when > > this bug will be fixed? > > The workaround script isn't there any longer. It's still on github and it's still working, see 5th comment.
Another workaround is to change your hotkey to custom command: /usr/bin/krunner --replace
(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?
(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.
*** Bug 499477 has been marked as a duplicate of this bug. ***
*** Bug 499722 has been marked as a duplicate of this bug. ***
*** Bug 499889 has been marked as a duplicate of this bug. ***
*** Bug 499974 has been marked as a duplicate of this bug. ***
*** Bug 500198 has been marked as a duplicate of this bug. ***
*** Bug 500266 has been marked as a duplicate of this bug. ***
*** Bug 500493 has been marked as a duplicate of this bug. ***
*** Bug 500510 has been marked as a duplicate of this bug. ***
*** Bug 500567 has been marked as a duplicate of this bug. ***
*** Bug 500721 has been marked as a duplicate of this bug. ***
As a workaround, one can switch the QT QPA platform to xcb. e.g. QT_QPA_PLATFORM=xcb krunner --replace or systemctl --user edit plasma-krunner.service # and put the flowing snippet to set the environment just for this service. [Service] Environment=QT_QPA_PLATFORM=xcb (sorry for the noise, but some ppl might be interested in this.)
*** Bug 502015 has been marked as a duplicate of this bug. ***