Bug 451597 - KDE Connect "falls asleep" after a while of not opening the main window, despite having a tray icon.
Summary: KDE Connect "falls asleep" after a while of not opening the main window, desp...
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: windows-application (show other bugs)
Version: 1.10
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: brute4s99
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-17 00:14 UTC by Tommy Sebestyen
Modified: 2023-03-04 13:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tommy Sebestyen 2022-03-17 00:14:31 UTC
SUMMARY
After KDE has been open for a while (not sure the exact time frame, maybe the better part of a day.) it will "fall asleep" and other devices will no longer see it as available until I click the tray icon and open the main window again.  It'll then stay active for a while, until it "falls asleep" again.  This is particularly annoying if I've been lying on my bed on my phone and want to send a link/file/whatever to my computer to look at once I get up.

STEPS TO REPRODUCE
1. Open the app.
2. Wait a while.
3. Try to send a file from another device.
4. Notice that the Windows device(s) are missing.
5. Get off your sweaty bum and walk over to the Windows device(s) in question.
6. Click the tray icon to open the main window.
7. Refresh the list on the other device and notice that the Windows device(s) are now available.
8. Become annoyed.

OBSERVED RESULT
Windows clients aren't available after a while, causing me to have to get off my butt and go fix it.

EXPECTED RESULT
Windows clients (or any client) should be available at all times, so that I can use any of the plugins at any time, instead of needing to go and "wake up" the client, at which point I might as well just do whatever action from there.

SOFTWARE/OS VERSIONS
Windows: Version 21H2 (OS Build 19044.1586)
There isn't a way to view the version number in the Windows version, as far as I can tell, but I have JUST updated it from the Windows Store a few days ago.  So it should be the latest version as of this post.
Comment 1 valdikss 2022-09-17 14:16:22 UTC

*** This bug has been marked as a duplicate of bug 442790 ***
Comment 2 valdikss 2022-09-17 14:19:37 UTC
I believe that https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/497 should fix the issue. I'm not completely sure, but several hour testing with this patch did not trigger this behavior.
Comment 3 Albert Vaca Cintora 2023-03-04 13:07:15 UTC
Git commit bd796836c50bb8293ff6422d0bf24a34cac9c8ba by Albert Vaca Cintora, on behalf of ValdikSS ValdikSS.
Committed on 04/03/2023 at 13:06.
Pushed by albertvaka into branch 'master'.

Enable socket Keep-Alive on Windows

Windows does not use setsockopt for keep-alive configuration,
requiring WSAIoctl call.

https://learn.microsoft.com/en-us/windows/win32/winsock/sio-keepalive-vals
Related: bug 442790

M  +24   -0    core/backends/lan/lanlinkprovider.cpp

https://invent.kde.org/network/kdeconnect-kde/commit/bd796836c50bb8293ff6422d0bf24a34cac9c8ba