KRunner stops working after pressing an escape key on Plasma 6

Help
, ,
1

Hi! I am using Fedora Linux KDE 40 on my laptop. Since yesterday, I have been observing a weird behavior of Krunner; it suddenly stops working after some time.

From the system monitor, I have checked that an instance of Krunner is running, and inside the /usr/share/dbus-1/services/ directory, the service file for Krunner is present; here are its contents.

[D-BUS Service]
Name=org.kde.krunner
Exec=/usr/bin/krunner --daemon
SystemdService=plasma-krunner.service

I have assigned the shortcut Alt + space to launch Krunner. For the first 2 to 3 times; it launches properly. However, when I hit the escape key or a mouse click to close the pop-up, the pop-up of Krunner does not launch anymore.

Which issue might be causing this annoyance? Any help on this would be appreciated.

1 Like
2

I’m still having this issue in Plasma 6.1.5.

3

I’m seeing the same thing after upgrading from Kubuntu 24.04 LTS to 24.10 with Plasma 6.1.5. I’m also using Wayland for the first time now, although I’m not sure if that is making a difference in the behavior.

When it isn’t responding I have to kill the krunner process and then Alt+Space will start launching it again.

4

I am experiencing the same issue. I’ve found that repeatedly hitting the shortcut key (ALT+Spacebar in my case) it will eventually come back up and works until I switch to another window; sometimes immediately or sometimes a bit later but it will always at some point fail to launch the first time I hit the shortcut keys.

When it fails to launch, this message is logged every time I hit the shortcut key until it launches:

krunner[1618]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5912e080aba0

Potentially relevant:

System:
  Kernel: 6.12.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc
  Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A wm: kwin_wayland with: krunner
    vt: 1 dm: SDDM Distro: Arch Linux
CPU:
  Info: 8-core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP smt: enabled
    arch: Zen 2 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080] vendor: Micro-Star MSI
    driver: nvidia v: 565.57.01 arch: Turing pcie: speed: 8 GT/s lanes: 16
    ports: active: none off: DP-2 empty: DP-1, DP-3, HDMI-A-1, Unknown-2
    bus-ID: 2d:00.0 chip-ID: 10de:1e82 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: 0
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 565.57.01
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
  API: Vulkan v: 1.3.295 layers: 2 surfaces: xcb,xlib,wayland device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:1e82
5

Hi - I suspect folks here are running into the following bug: 480800 – On Wayland KRunner and other Plasma pop-ups are intermittently not opening with eglSwapBuffers errors

Which, as best as folks can figure out now, seems to be an upstream bug in either Qt or (as most folks who have reported explicitly mentioned having Nvidia graphics) the Nvidia GPU drivers.

Hope that helps in the meantime,

6

I have notice as have others that since Plasma 6 KRunner likes to stop working and one has to launch Konsole enter krunner up to 3 times to get it to behave again. I’m assuming I’m far from the only one that is a heavy KRunner and am more than a bit tired of this behavior. Is there an alternative with the same behavior for being able to simply type on the desktop and have it open and do the searches? Thanks