Plasma 6 Krunner failing to start

Help
1

Krunner failing to start after few successful starts, can’t figure out what exactly happens. Fail to start with shortcut and with command line (outputs nothing)
systemctl status --user plasma-krunner logs:

июл 31 02:36:58 server krunner[15078]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
июл 31 02:36:58 server krunner[15078]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
июл 31 02:36:58 server krunner[15078]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
июл 31 02:36:58 server krunner[15078]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
июл 31 02:36:58 server krunner[15078]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
июл 31 02:36:58 server krunner[15078]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
июл 31 02:37:00 server krunner[15078]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5d4c5f179500
июл 31 02:37:01 server krunner[15078]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5d4c5f179500
июл 31 02:37:01 server krunner[15078]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5d4c5f179500
июл 31 02:37:02 server krunner[15078]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5d4c5f179500

after killing krunner, it starts alright (a few times)

2

the error is 0x300d (EGL_BAD_SURFACE)

3

is it fixable ? or should i wait for new release ?

4

I’m having the the issue. Were you able to find a solution?

krunner --replace eventually outputs:

qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5f44582432b0