Kill kdeconnect on reboot/shutdown

so rebooting/shutting down takes quiet a few seconds than necessary ;-). i’ve narrowed it down to kdeconnectd delaying the shutdown process.


Dec 17 23:36:07 koshika-inspiron-5520 dbus-daemon[1055]: [session uid=1000 pid=1055] Successfully activated service 'org.kde.kdeconnect'                             │
│Dec 17 23:36:07 koshika-inspiron-5520 kwin_x11[1091]: QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHan│
│Dec 17 23:36:07 koshika-inspiron-5520 kwin_x11[1091]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8478, resource id: 6294097, major code: 18 (Cha│
│Dec 17 23:36:07 koshika-inspiron-5520 kded5[1087]: Service  "org.kde.StatusNotifierHost-1138" unregistered                                                           │
│Dec 17 23:36:07 koshika-inspiron-5520 kdeconnectd[38137]: kdeconnect.core: Could not query capabilities from notifications server                                    │
│Dec 17 23:36:17 koshika-inspiron-5520 ksmserver[1113]: org.kde.kf5.ksmserver: SmsDie timeout, client  "/usr/lib/kdeconnectd" ( 102031ef1eb1a5000163976436700000011130│
│Dec 17 23:36:17 koshika-inspiron-5520 kwin_x11[1091]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9637, resource id: 23068679, major code: 18 (Ch│
│Dec 17 23:36:17 koshika-inspiron-5520 org.kde.kdeconnect[38137]: ICE default IO error handler doing an exit(), pid = 38137, errno = 25                               │
│Dec 17 23:36:17 koshika-inspiron-5520 systemd-logind[599]: System is powering down.                                                                                  │

anyone with good suggestions, how to deal with this, maybe issue a systemd killall command when the reboot/shutdown process is initiated, thanks

systemd is already doing that. First it sends a SIGTERM to properly shut down everything ─ effectively, it tells applications to terminate and clean up after themselves ─ and then ultimately it sends a SIGKILL so as to catch the processes that didn’t.

will creating a specific systemd unit file to handle (kill kdeconnect) on targets; be bad practise

It would work, but I would recommend against it, because a SIGKILL is never clean. The application won’t be able to save its state and properly close whatever files it has open.

You could compare it to swatting a nasty fly with a sledgehammer. :wink:

i agree, additional 10s waiting on infrequent reboot/shutdown should not be a worry, just that when i’m in a hurry, its bit of nuisance. i would see if it works, and get rid of the “dirty” killing anyway. thanks

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.