Bug 482014 - Krunner won't start after login using the keyboard shortcut - error is says name not provided by any .service files
Summary: Krunner won't start after login using the keyboard shortcut - error is says n...
Status: RESOLVED DUPLICATE of bug 481940
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 6.0.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-29 11:57 UTC by thebluequasar
Modified: 2024-03-03 19:14 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thebluequasar 2024-02-29 11:57:47 UTC
SUMMARY
after I log in to Plasma Desktop (v6.0, starting with empty session) pressing the keyboard shortcut will not launch krunner, instead this error message is shown: The name org.kde.krunner was not provided by any .service files. However, if I start krunner from a terminal, it does launch and its process is running, the keyboard shortcut also works as expected. Running the krunner from the terminal produces some warnings though, I've pasted them in the additional information below.

STEPS TO REPRODUCE
1. Login to Plasma Desktop (v6.0) with an empty session
2. Press Alt+Space (or any combination you've assigned to krunner)
3. You'll get this error message: Launching Krunner (Failed) - The name org.kde.krunner was not provided by any .service files

OBSERVED RESULT
Krunner won't launch using the keyboard shortcut after logging in to Plasma (v6.0)

EXPECTED RESULT
Krunner should run as expected using the keyboard shortcut on Plasma 6.0 without the need for any sort of manual tweaking

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon (User)
KDE Plasma Version: 6.0
KDE Frameworks Version:6.0 
Qt Version: 6.6.2
Kernel: 6.5.0-21 generic 64bit

ADDITIONAL INFORMATION
Starting krunner from a terminal produces this output for me: 
` Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QStri
ng,QString) 
QObject::startTimer: Timers cannot be started from another thread  `

If I can provide any other information that might be useful, please give me a brief instruction on how to obtain them (the commands or apps used), and I'll post them here.
Comment 1 Nicolas Fella 2024-02-29 11:59:26 UTC

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