Bug 500567 - Krunner stops working after using it once
Summary: Krunner stops working after using it once
Status: RESOLVED DUPLICATE of bug 480800
Alias: None
Product: krunner
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.3.1
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-22 10:11 UTC by alicftcdev
Modified: 2025-02-22 10:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
result of QT_LOGGING_RULES="*.debug=true" krunner --replace > kdelog.txt 2>&1 (1.73 MB, text/plain)
2025-02-22 10:11 UTC, alicftcdev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description alicftcdev 2025-02-22 10:11:56 UTC
Created attachment 178721 [details]
result of QT_LOGGING_RULES="*.debug=true" krunner --replace > kdelog.txt 2>&1

SUMMARY

Krunner stops working after using it once until the systemd service is restarted

STEPS TO REPRODUCE
1. Launch Krunner
2. Exit Krunner
3. Try launching Krunner again

OBSERVED RESULT

It simply won't open

EXPECTED RESULT

Krunner should open as many times as needed without restarting the service

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.3.1
KDE Plasma Version: 6.3.1
KDE Frameworks Version:  6.11.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION

Tried in Wayland with Nvidia GPU.

Systemd log:
Feb 22 11:00:58 endeavouros krunner[6293]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDon>
Feb 22 11:00:58 endeavouros krunner[6293]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkReq>
Feb 22 11:00:58 endeavouros krunner[6293]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDon>
Feb 22 11:00:58 endeavouros krunner[6293]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkReq>
Feb 22 11:00:58 endeavouros krunner[6293]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDon>
Feb 22 11:00:58 endeavouros krunner[6293]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkReq>
Feb 22 11:00:58 endeavouros krunner[6293]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::checkDon>
Feb 22 11:00:58 endeavouros krunner[6293]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Feb 22 11:01:07 endeavouros krunner[6293]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x57af942889f0
Feb 22 11:01:08 endeavouros krunner[6293]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x57af942889f0

Log after launching in terminal:
 ~ >>> krunner
QThreadStorage: Thread 0x60e31cbdc030 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x60e31cbdc030 exited after QThreadStorage 4 destroyed
QThreadStorage: Thread 0x60e31cbdc030 exited after QThreadStorage 3 destroyed

You can find the backtrace from the command 
`~ >>> QT_LOGGING_RULES="*.debug=true" krunner --replace > kdelog.txt 2>&1` 
in the attachments.
Comment 1 Antonio Rojas 2025-02-22 10:16:56 UTC

*** This bug has been marked as a duplicate of bug 480800 ***