SUMMARY Using krunner in the nvidia-wayland session results in no results being returned and in a general lag when writing on the input field. This only happens using nvidia-wayland, intel session is working fine. STEPS TO REPRODUCE 1. Login into a wayland session utilizing nvidia hardware. 2. Open krunner 3. Write any word OBSERVED RESULT KRunner doesn't show its result window. EXPECTED RESULT Options should be displayed below the input text SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 Kernel Version: 5.1.4-arch1-1-ARCH OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 23.5 GiB of RAM ADDITIONAL INFORMATION Let me know how can I extract any extra log or data from krunner to reproduce this issue.
Sorry for taking a while to look into this, however it would seem krunner's QSGRenderThread is getting stuck in eglSwapBuffers waiting for a wl_surface::frame event. I think this is a similar issue to what I tried to address in https://phabricator.kde.org/D18307. It looks like if Compositor::performCompositing detects that no windows have been damaged, it will return early without servicing any frame events. Just trying to confirm this and figure out the best way to get around the issue.
I plan on reworking the compositing pipeline. Maybe it makes sense to look for a solution of the issue in this context, Erik (in general I would appreciate your feedback on the overall plan anyway). https://phabricator.kde.org/T11071
Is this still reproducible on Plasma 5.21?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!