Created attachment 123796 [details] Picture of the error SUMMARY Windows Client (installed from the nightly binary and I'm using the build 196) stops working correctly when it receives a notification from the phone. It's not able to connect anymore until I close the application and I reopen it. The error is "Failed to execute program org.kde.kdeconnect: no such file or directory" and it's on the PC Name field. I'm attaching a screenshot. STEPS TO REPRODUCE 1. Open KDE Connect on Windows (I assume the phone is already paired) 2. Enable the mirroring of notifications. 3. Receive a notification on the phone, it can be a message from a friend. OBSERVED RESULT The phone disappears from the Windows Client and it shows an error. EXPECTED RESULT It should show the notification and... work without crashing. SOFTWARE/OS VERSIONS Windows: 10 v.1903 (build SO 18362.418) KDE Connect Nightly build 196 (even the older ones crashed)
Same for me, even though sometimes it pushes notifications without any issue. It also seems to crash sometimes when resuming from suspend. Windows Event view links crashes with errors with these modules: - C:\WINDOWS\SYSTEM32\ntdll.dll (kdeconnectd.exe) - C:\WINDOWS\System32\ucrtbase.dll (kdeconnect-indicator.exe) Starting kdeconnectd.exe from a terminal, I get this output when it crashes: kdeconnect.plugin.contacts: sendRequest: Sending "kdeconnect.contacts.request_all_uids_timestamps" true kdeconnect.plugin.notification: Not found noti by internal Id: "0|com.whatsapp|11|null|10183" kdeconnect.plugin.notification: Not found noti by internal Id: "0|com.whatsapp|11|null|10183" kdeconnect.core: FileTransferJob Downloading payload to QUrl("file:///C:/Users/username/AppData/Local/Temp/kdeconnect_username/e50dd13a9340ff83a4ab7bbbde49aeba") size: 31338 QMetaObject::invokeMethod: No such method KIO::StoredTransferJob::slotDataReqFromDevice() kf5.kio.kio_file: readData() returned -1 I'm using release binaries and this crashes were not happening when I was building it with craft (a year ago). Or else, it seemed like kdeconnectd.exe was crashing, but it was started again as soon as it crashed.
Please try out the latest build from https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/ and let me know how it goes! Some relevant improvements:- - battery plugin does not crash kdeconnect anymore - resume from suspend should not crash kdeconnect anymore - notifications should not crash kdeconnect anymore If there are any crashes feel free to revert to me through this thread!
(In reply to brute4s99 from comment #2) Still broken for me after resuming from suspend. https://i.imgur.com/ui9MzLR.png After a while, this message appears where the device name should be: "Did not receive a reply. Possible causes include: the remote app..." I didn't test it enough to comment on the other crashes I used to have.
It crashed with error "Failed to spawn child". It worked fine for a while, I received some notifications. After a while I checked and it wasn't connected anymore.
The daemon crash is still not perfect. However, expect that the "Failed to spawn child" error will not show up anymore.
are there any issues left regarding this bug?
(In reply to brute4s99 from comment #6) > are there any issues left regarding this bug? I am experiencing the same issue with the version that is available from Microsoft Score. I tried the latest build but found it unusable as the controls in the user interface were totally misaligned and text missing some characters. The strange thing is that on 3 other machines, there are no such issues. It's only on 1 of my machines. All machines are fully updated and are running latest VC++ runtimes.