| Summary: | wake up from sleep/ logoff kills kdeconnect | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | johnathan <testing1237a-c> |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugs.kde.org, kde.org, oded, robin |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
johnathan
2019-06-10 05:06:39 UTC
I can confirm I am getting this bug too, using UbUntu 20.04, kdeconnect 20.12 and a recent debug build of the kdeconnect Android app. At present I have to close kdeconnect-sms on my laptop, then restart it manually, I assume doing so kills the existing, hanging connection then creates a new network connection as soon as I relaunch it. Android version 1.17 I'm having the same issue with KDE Connect. Once I opened the GUI of KDE Connect from tray, it reconnects to the phone without issues. Maybe they should drop the XDG-Autostart desktopfile and create a proper global systemd-user-unit, that includes dependencies for the suspend/resume targets also... Maybe ill make such a unit myself in due time and post somewhere or here... The kdeconnectd should still be running after the system comes back from sleep, which should make it connect to the device once the network is up. Maybe the service has crashed? I can't reproduce this issue with KDE Connect 23.04.3 on Plasma 5.27.7 If you can still reproduce this issue - can you please check if the kdeconnectd process is running after coming back from sleep and not connecting to the phone? We don't need an autostart, kdeconnect is dbus-activated so simply trying to use kdeconnect after it has crashed should start it. This bug is very old and I don't think it can be reproduced nowadays, closing. |