Plasma - KRunner stops working intermittently

Issues & Assistance
1

Hello, very new here, just installed CachyOS today. :blush:
I noticed some time after a fresh boot or login, the KRunner (I hope it’s the correct name for the process that allows you start typing an application name on the desktop and it finds it for you and lets you launch it that way) just stops working.

With my quite limited knowledge of Linux, I tried to check for any errors in journalctl and I found a lot of the following errors:

krunner[1249]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo" : "org.freedesktop.DBus.Error.NotSupported" ""

krunner[1249]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x596664a9e910

Is that a known error, guys? Also, is there something I can do to fix it? I tried googling the forum and so far haven’t been able to find out whether you’ve already tackled this one.

Thank you :slightly_smiling_face:

2

Yea this has been an issue with Krunner since Plasma 6.0. Some Say nVidia related others think it’s Wayland related.

3

Thank you for the info. Hopefully, they will fix it soon :+1:

In the meantime, I’ll try login into an X11 session to find out whether it really does happen only in Wayland or not. Maybe I’ll be lucky :see_no_evil:

1 Like
4

Even with x11 being a dead project it is still far superior to Wayland. As nice as Plasma 6.0 and up is choosing to make Wayland the default was a huge mistake.

5

@CCG Do you have 2K or 4K screens? Without Wayland they are near to unusable.

6

I have a 4k 32 inch under Wayland on a nvidia 3060.

Dell S3221qs

7

Using my 4K screen with x11 just fine.

8

I think it has to be related to NVIDIA drivers. On my laptop with integrated intel graphics works just fine. But wayland on my PC with NVIDIA card has the same issue as you.

9

There isa a workaround for this. You still get the error message running Krunner from Konsole, but after you run it from Konsole it keeps working even through logoffs and reboots.

10

Thanks, I’ll try this. :slightly_smiling_face: :+1:

1 Like
11

For me it wasn’t persistent using the CLI. However, this is a workaround which made it persistent for me:

systemctl --user edit plasma-krunner.service

Add (where the cursor is):

[Service]
Environment=QT_QPA_PLATFORM=xcb

Reboot (or restart the service).

Now, it should always work, even after a reboot (for that user).

Apparently, it’s QT/NVIDIA related issue and none of them really seem to move forward as it’s reported on both sides.