| Summary: | Error while communicating with the global shortcuts service on deiban trixie | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | David Blbulyan <blbulyandavbulyan> |
| Component: | kcm_keys | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.10 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
David Blbulyan
2024-03-03 09:26:00 UTC
What happens if you run manually kcmshell6 keys What does systemctl status --user plasma-kglobalaccel.service say? Finally if the service is not running what happens if you run /usr/lib/x86_64-linux-gnu/libexec/kglobalacceld manually? Sorry I just saw this is plasma 5, so instead of kglobalacceld in libexec, try running kglobalaccel5 which is in PATH (In reply to David Redondo from comment #2) > Sorry I just saw this is plasma 5, so instead of kglobalacceld in libexec, > try running kglobalaccel5 which is in PATH david@DebianW ~ systemctl status --user plasma-kglobalaccel.service ● plasma-kglobalaccel.service - KDE Global Shortcuts Server Loaded: loaded (/usr/lib/systemd/user/plasma-kglobalaccel.service; static) Active: active (running) since Tue 2024-03-05 08:35:11 +04; 2min 29s ago Main PID: 3059 (kglobalaccel5) Tasks: 3 (limit: 18751) Memory: 12.3M (peak: 30.0M) CPU: 348ms CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kglobalaccel.service └─3059 /usr/bin/kglobalaccel5 мар 05 08:35:11 DebianW systemd[2737]: Starting plasma-kglobalaccel.service - KDE Global Shortcuts Server... мар 05 08:35:11 DebianW systemd[2737]: Started plasma-kglobalaccel.service - KDE Global Shortcuts Server. мар 05 08:35:11 DebianW kglobalaccel5[3059]: kf.globalaccel.kglobalacceld: No desktop file found for service "clementine.desktop" мар 05 08:35:11 DebianW kglobalaccel5[3059]: QDBusObjectPath: invalid path "/component/_home_david__аг_уз_и_eclipse_installer__desktop" мар 05 08:35:11 DebianW kglobalaccel5[3059]: QDBusObjectPath: invalid path "/component/_еи_ста__и__вать_H_A_W_X__2_desktop" мар 05 08:35:32 DebianW kglobalaccel5[3059]: QDBusObjectPath: invalid path "/component/_home_david__аг_уз_и_eclipse_installer__desktop" мар 05 08:35:32 DebianW kglobalaccel5[3059]: QDBusObjectPath: invalid path "/component/_еи_ста__и__вать_H_A_W_X__2_desktop" мар 05 08:35:32 DebianW kglobalaccel5[3059]: QDBusConnection: error: could not send reply message to service "": Marshalling failed: Invalid object path pa> мар 05 08:35:36 DebianW kglobalaccel5[4238]: Omitting both --window and --windowclass arguments is not recommended Seems like we've got a bad object path. Could you please paste the output of qdbus --literal org.kde.kglobalaccel /kglobalaccel org.kde.KGlobalAccel.allComponents (In reply to David Redondo from comment #4) > Seems like we've got a bad object path. Could you please paste the output of > qdbus --literal org.kde.kglobalaccel /kglobalaccel > org.kde.KGlobalAccel.allComponents ✘ david@DebianW ~ qdbus --literal org.kde.kglobalaccel /kglobalaccel org.kde.KGlobalAccel.allComponents Error: org.freedesktop.DBus.Error.NoReply Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 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! 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! |