SUMMARY Desktop application crashes, replacing machine name with "Failed to execute program org.kde.kdeconnect: The system cannot" in the desktop application. Service stops responding from phone application STEPS TO REPRODUCE 1. Download nightly build from https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/kdeconnect-kde-master-146-windows-msvc2017_64-cl.exe and install 2. Pair with device (either initiated Windows -> Phone or Phone -> Windows) 3. Ping device Windows -> Phone 4. Crash OBSERVED RESULT Replaced machine name with "Failed to execute program org.kde.kdeconnect: The system cannot" in the desktop application. Service stops responding, disconnecting connected devices. EXPECTED RESULT Ping on Phone or Ping on Desktop application SOFTWARE/OS VERSIONS Windows: Windows 10 Enterprise 1703 Android: 1.13 ADDITIONAL INFORMATION
Last few lines from kdeconnectd run in a command prompt: Command Line: SnoreToast.exe -t "KDE Connect Daemon" -m "Pairing request from Personal phone" -p C:/Users/Jon/AppData/Local/Temp/kdeconnect.daemon-jopAxT/0.png -appID kdeconnect.daemon -pid 3916 -id 0 -pipename \\.\pipe\1580314081 -b Accept;Reject discarding unsupported packet "kdeconnect.runcommand.request" for "Personal phone" discarding unsupported packet "kdeconnect.mpris" for "Personal phone" Notifications are disabled Reason: DisabledForUser Please make sure that the app id is set correctly. Command Line: SnoreToast.exe -t Slack -m "SomeText" -p C:/Users/Jon/AppData/Local/Temp/kdeconnect.daemon-jopAxT/1.png -appID kdeconnect.daemon -pid 3916 -id 1 -pipename \\.\pipe\1580314081 -b Reply Notifications are disabled Reason: DisabledForUser Please make sure that the app id is set correctly. Command Line: SnoreToast.exe -t Slack -m "SomeText" -p C:/Users/Jon/AppData/Local/Temp/kdeconnect.daemon-jopAxT/-2.png -appID kdeconnect.daemon -pid 3916 -id -2 -pipename \\.\pipe\1580314081 -b Reply Application then stops. I noted that notifications were disabled on my system. Enabling the notifications and restarting kdeconnectd now has a slightly longer lifespan: kdeconnect.core: TCP connection done (i'm the existing device) kdeconnect.core: Starting server ssl (I'm the client TCP socket) kdeconnect.core: Socket successfully established an SSL connection kdeconnect.core: It is a known device "Personal phone" kdeconnect.core: Not loading plugin "kdeconnect_remotesystemvolume" because device doesn't support it kdeconnect.core: Not loading plugin "kdeconnect_remotecommands" because device doesn't support it kdeconnect.core: Not loading plugin "kdeconnect_lockdevice" because device doesn't support it kdeconnect.core: creating pairing handler for "someid" kdeconnect.core: Unpair request kdeconnect.plugin.notification: Destroying NotificationsPlugin kdeconnect.core: Unpair request kdeconnect.core: Unpair request kdeconnect.core: Unpair request kdeconnect.core: Unpair request kdeconnect.core: Pair request kdeconnect.plugin.battery: Deleting stale BatteryDbusInterface for "Personal phone" discarding unsupported packet "kdeconnect.runcommand.request" for "Personal phone" discarding unsupported packet "kdeconnect.mpris" for "Personal phone" kdeconnect.core: FileTransferJob Downloading payload to QUrl("file:///C:/Users/Jon/AppData/Local/Temp/kdeconnect_Jon/someid") size: 14430 QMetaObject::invokeMethod: No such method KIO::StoredTransferJob::slotDataReqFromDevice() kdeconnect.core: Finished transfer QUrl("file:///C:/Users/Jon/AppData/Local/Temp/kdeconnect_Jon/someid") And then, crash again.
Hi Jon! I hope this reply finds you in good health! There has been some improvement on the stability side of things for the Windows port in the last few weeks, please try out the latest build from https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/ and let us know how it goes!
Wow, yes, this is a fantastic step up. I'm resolving this issue as it's all working fine!