| Summary: | On Wayland KRunner and other Plasma pop-ups are intermittently not opening with eglSwapBuffers errors | ||
|---|---|---|---|
| Product: | [Plasma] krunner | Reporter: | gtpepi |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | CLOSED UPSTREAM | ||
| Severity: | normal | CC: | achilleas.k, alexander.lohnau, aubergine, cummingcowgirl, kdedev, krystian, leanguedes, matt.fagnani, natalie_clarius, nate, nishant.119, rabin, vincent, wank_my_willy1, xaver.hugl |
| Priority: | HI | Keywords: | wayland |
| Version: | 5.93.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=490813 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
gtpepi
2024-02-03 19:55:23 UTC
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. |