Bug 437182 - Krunner systemd service (plasma-krunner.service) failed to start. Krunner doesn't open.
Summary: Krunner systemd service (plasma-krunner.service) failed to start. Krunner doe...
Status: RESOLVED WORKSFORME
Alias: None
Product: krunner
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.21.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Alexander Lohnau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-15 23:20 UTC by foss
Modified: 2022-07-18 04:36 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description foss 2021-05-15 23:20:24 UTC
SUMMARY
plasma-krunner.service user service failed. Apparently some external drives couldn't be found?! idk

STEPS TO REPRODUCE
1. Enable the "systemd startup feature"
2. Check failed user units
3. 

OBSERVED RESULT
plasma-krunner.service has a failed status. I can't start krunner through the shortcut Alt+Space. I mean Krunner doesn't show up.

EXPECTED RESULT
Krunner shows up after the shortcut is pressed.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Graphics Platform: Wayland
 

ADDITIONAL INFORMATION
----------------------------------------
systemctl --user --failed
----------------------------------------
UNIT                   LOAD   ACTIVE SUB    DESCRIPTION
● plasma-krunner.service loaded failed failed KRunner

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

-----------------------------------------------------------
systemctl --output=cat --user status plasma-krunner.service
-----------------------------------------------------------
× plasma-krunner.service - KRunner
Loaded: loaded (/usr/lib/systemd/user/plasma-krunner.service; static)
Active: failed (Result: exit-code) since Sun 2021-05-16 00:34:48 CEST; 25min ago
Process: 26621 ExecStart=/usr/bin/krunner (code=exited, status=1/FAILURE)
Main PID: 26621 (code=exited, status=1/FAILURE)
CPU: 13min 56.233s

org.kde.kf5.kwindowsystem.kwayland: This compositor does not support the Plasma Window Management interface
org.kde.kf5.kwindowsystem.kwayland: Failed to recreate shadow for View(0x7ffc82935bc0)
kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/drives/SanDisk_Extreme_Portable_SSD_2039D0806132"
kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/drives/SanDisk_Extreme_Portable_SSD_2039D0806132"
kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/drives/ST500LM012_HN_M500MBB_S2RYJ9AD304206"
kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/drives/ST500LM012_HN_M500MBB_S2RYJ9AD304206"
The Wayland connection broke. Did the Wayland compositor die?
plasma-krunner.service: Main process exited, code=exited, status=1/FAILURE
plasma-krunner.service: Failed with result 'exit-code'.
plasma-krunner.service: Consumed 13min 56.233s CPU time.
Comment 1 David Edmundson 2022-06-18 07:51:48 UTC
The first warnings are harmless then we get:

The Wayland connection broke. Did the Wayland compositor die?
plasma-krunner.service: Main process exited, code=exited, 

Which implies kwin closed.  Can you confirm this is still an issue.
Comment 2 Bug Janitor Service 2022-07-03 04:36:51 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-07-18 04:36:46 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!