SUMMARY This is a long-time bug I've experienced on Windows (at least 6 months). STEPS TO REPRODUCE 1. Run `cmd /k "cd C:\Program Files\KDE Connect\bin & kdeconnectd.exe"` (opens kdeconnectd with persistent command line) 2. Run `nc localhost 1716` (on linux subsystem if you don't have netcat). 3. kdeconnectd.exe should print to stderr: "kdeconnect.core: LanLinkProvider newConnection\n". 4. Wait approximately 20-30 minutes, try netcat again. OBSERVED RESULT kdeconnectd.exe will initially work as intended. All connections to port 1716 will be logged to the console. kdeconnect-indicator.exe will show a list of paired devices, all functions work. After about 20 minutes, kdeconnectd stops replying to network commands. Connections to :1716 will still be accepted, but will no longer be logged to the console. No inquiries from kdeconnect-indicator will be answered. And the client on Android will show "The paired device is not reachable". kdeconnectd.exe must be killed and restarted. It fails so predictably that I have a script that monitors kdeconnectd.exe's stderr, tries a TCP connection to 1716 every 10 mins, and kills and restarts it if "LanLinkProvider newConnection" isn't written after 1 second. EXPECTED RESULT Should work as expected all year long. SOFTWARE/OS VERSIONS Windows: 10.0.17763 Build 17763 ADDITIONAL INFORMATION I'm on a wired connection. The only feature I use (occasionally) is remote input.
Created attachment 120416 [details] screenshot Did not receive a reply. Possible causes include: the remote app
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
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!