Summary: | kglobalaccel breaks after logging out | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kglobalaccel | Reporter: | Fabian Vogt <fabian> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bugseforuns, elman, henri, kde, mpagano, nate, sknauss |
Priority: | NOR | ||
Version: | 5.77.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Fabian Vogt
2020-11-20 20:38:37 UTC
This is probably "caused" by "systemd dbus activation". A definitely related merge request was started: https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/10 Git commit 25e84f3f6ac54097d9c021705dc18b187352fa02 by David Edmundson. Committed on 18/12/2020 at 17:29. Pushed by davidedmundson into branch 'master'. Avoid autostarting kglobalaccel when shutting down Order of our service teardown is somewhat undefined. kglobalaccel5 can be closed before plasmashell. On plasma exit we call setInactive/unregister on various kglobalaccel actions and accidentally spawn kglobalaccel again. If kglobalaccel is already closed, our actions aren't registered. There is no point waking it up to try and remove an action. Use of the setAutoStartService flag was chosen over checking if the kglobalaccel service is still registered as that is still racey. This was always slightly broken, but changes in the ecosystem means the effect has worsened. M +25 -3 src/kglobalaccel.cpp M +3 -0 src/kglobalaccel_p.h https://invent.kde.org/frameworks/kglobalaccel/commit/25e84f3f6ac54097d9c021705dc18b187352fa02 (In reply to David Edmundson from comment #3) > Git commit 25e84f3f6ac54097d9c021705dc18b187352fa02 by David Edmundson. > Committed on 18/12/2020 at 17:29. > Pushed by davidedmundson into branch 'master'. I've adding this patch on top of 5.56.0 and tested it. But systemd is still restarting kglobalaccel: while shutting down the computer: Dez 29 22:48:12 xxx systemd[1]: Stopping Session 3 of user Me Dez 29 22:48:12 xxx systemd[5622]: plasma-kglobalaccel.service: Main process exited, code=exited, status=1/FAILURE Dez 29 22:48:12 xxx systemd[5622]: plasma-kglobalaccel.service: Failed with result 'exit-code'. Dez 29 22:48:12 xxx systemd[5622]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 1. Dez 29 22:48:12 xxx systemd[5622]: Stopped KDE Global Shortcuts Server. Dez 29 22:48:12 xxx systemd[5622]: Starting KDE Global Shortcuts Server... Dez 29 22:48:12 xxx kglobalaccel5[12379]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Dez 29 22:48:12 xxx kglobalaccel5[12379]: Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-eg> Dez 29 22:48:12 xxx systemd[5622]: plasma-kglobalaccel.service: Main process exited, code=killed, status=6/ABRT Dez 29 22:48:12 xxx systemd[5622]: plasma-kglobalaccel.service: Failed with result 'signal'. Dez 29 22:48:12 xxx systemd[5622]: Failed to start KDE Global Shortcuts Server. (In reply to Sandro Knauß from comment #4) > (In reply to David Edmundson from comment #3) > > Git commit 25e84f3f6ac54097d9c021705dc18b187352fa02 by David Edmundson. > > Committed on 18/12/2020 at 17:29. > > Pushed by davidedmundson into branch 'master'. > > I've adding this patch on top of 5.56.0 and tested it. But systemd is still > restarting kglobalaccel: while shutting down the computer: > > Dez 29 22:48:12 xxx systemd[1]: Stopping Session 3 of user Me > Dez 29 22:48:12 xxx systemd[5622]: plasma-kglobalaccel.service: Main process > exited, code=exited, status=1/FAILURE > Dez 29 22:48:12 xxx systemd[5622]: plasma-kglobalaccel.service: Failed with > result 'exit-code'. > Dez 29 22:48:12 xxx systemd[5622]: plasma-kglobalaccel.service: Scheduled > restart job, restart counter is at 1. That seems like a slightly different issue - kglobalaccel exits with 1, so systemd tries to restart it. Question is why it exits with 1. *** Bug 430736 has been marked as a duplicate of this bug. *** *** Bug 431154 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 429426 *** |