SUMMARY Probably this report does not belong here - it concerns the experimental Windows builds. But I could not find a bugtracker for that. STEPS TO REPRODUCE 1. Install and configure application, on Windows and on Android phone. 2. On Android, send SMS to oneself. 3. Interact with the resulting Windows notification. So doing will, sometimes, trigger a crash. OBSERVED RESULT **Crash report** Log Name: Application Source: Application Error Date: 22/01/2020 00:33:42 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: T1650 Description: Faulting application name: kdeconnectd.exe, version: 0.0.0.0, time stamp: 0x5e26d367 Faulting module name: KF5Notifications.dll, version: 0.0.0.0, time stamp: 0x5e1f7554 Exception code: 0xc0000005 Fault offset: 0x000000000000c879 Faulting process ID: 0x1f30 Faulting application start time: 0x01d5d0b81c848354 Faulting application path: C:\Users\Nicholas\AppData\Local\KDE Connect\bin\kdeconnectd.exe Faulting module path: C:\Users\Nicholas\AppData\Local\KDE Connect\bin\KF5Notifications.dll Report ID: c4154dd9-b0da-420d-a409-8c3420ce8ddc Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-01-22T00:33:42.023780500Z" /> <EventRecordID>32759</EventRecordID> <Channel>Application</Channel> <Computer>T1650</Computer> <Security /> </System> <EventData> <Data>kdeconnectd.exe</Data> <Data>0.0.0.0</Data> <Data>5e26d367</Data> <Data>KF5Notifications.dll</Data> <Data>0.0.0.0</Data> <Data>5e1f7554</Data> <Data>c0000005</Data> <Data>000000000000c879</Data> <Data>1f30</Data> <Data>01d5d0b81c848354</Data> <Data>C:\Users\Nicholas\AppData\Local\KDE Connect\bin\kdeconnectd.exe</Data> <Data>C:\Users\Nicholas\AppData\Local\KDE Connect\bin\KF5Notifications.dll</Data> <Data>c4154dd9-b0da-420d-a409-8c3420ce8ddc</Data> <Data> </Data> <Data> </Data> </EventData> </Event> EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Windows: Windows 10 Pro 1903 (18362) Android: Lollipop ADDITIONAL INFORMATION KDEConnect, Windows version: kdeconnect-kde-master-278-windows-msvc2017_64-cl.exe (which is the latest nightly build, at the time of writing).
Hi! There have been some improvements on the stability side of things in the past few weeks. Could you please install the latest build from https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/ and let me know how it goes? You should not be getting the crash because of KF5Notifications.dll anymore.
I tried the new build. Thanks for the alert. My experience with that build has been as follows. There was no crash. However, much else was not good. I report those other problems in what remains of this comment. I know that ideally I would file separate bug reports for each problem but I am afraid that I am just not going to. Setting up on Windows ===================== Left clicking - even double left-clicking on the tray - does nothing. This is counter-intuitive, at least or especially for Windows users. (For I know that sometimes e.g. Cinnamon works like that.) Setting up on Android, via Fdroid ================================= I received this message: 'Error -2 The package archive file is invalid.' But the program seemed to install nonetheless. Pairing and VPNs ================ I had to disable the (Wireguard) VPN on both my phone and my Windows PC before either device could see the other. Perhaps that I need do those things only for *pairing* - see below. It seems easy to miss an incoming pair request: I sent the request from Android; on Windows, I did not see the request until, within the KDE Connect window (which was open already) I selected the name of the Windows device. The 'error trying to pair' message does not disappear once pairing is established. That confuses, pointlessly. A general comment on the UIs ============================ I found the UI on both Android and Windows unintuive. A sense of 'what now?' pervaded. On plug-ins and the plug-in list on Windows ========================================= The 'battery plug-in' appears not to work, perhaps because the Windows PC has no battery, because it is a desktop. But, ah, the phone's battery status appears . . in the KDE Connect tray context menu, on Windows. The icon for 'info' - next to each plug-in - is hard to recognise and gives one somewhat to think of downloading. There is no explanation in the plug-in list - on Windows - of what ticks mean. Does it mean installed? Does it mean active? Selecting a (/any) plug-in creates white text on a light blue background - an nearly unreadable combination. I sent myself a text message, from my phone. A notification appeared on the phone. I could find no notification anywhere on Windows. I was able to send a ping, via KDE Connect, from Windows to the phone. But vice-versa seemed not to work. I could ping even when, post-pairing, I enabled the Windows VPN; and I could do so even after, additionally, I had enabled the phone's VPN. (So those things are good.) Other ===== Does KDE Connect not have a start-with-Windows option? The user expects this. On my grey Windows taskbar, the icon for KDE Connect is hard to see. Initially I thought it was greyed-out - because I had not paired devices. But, no, it remains almost invisible grey. I will see whether I can add some screenshots to this report.
Created attachment 133248 [details] Screenshot
Created attachment 133249 [details] Screenshot
I spoke to soon about the absence of a crash, or at least what looks like a crash. For, when I plugged in my USB webcam, a little crash message window popped up: it said the connect program had stopped working. However, the program still showed in the system tray and still worked (well, worked as well as it was working before).
> Left clicking - even double left-clicking on the tray - does nothing. https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/351 =================================================== > It seems easy to miss an incoming pair request: I sent the request from Android; on Windows, I did not see the request until, within the KDE Connect window (which was open already) I selected the name of the Windows device. > The 'error trying to pair' message does not disappear once pairing is established. That confuses, pointlessly. Is this issue reproducible with the latest build? If yes, please make a separate bug report for it. =================================================== > I found the UI on both Android and Windows unintuive. A sense of 'what now?' pervaded. This patch hopes to aid that to a minor degree: https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/352 =================================================== > the phone's battery status appears . . in the KDE Connect tray context menu, on Windows. Is this issue reproducible with the latest build? If yes, please make a separate bug report for it. =================================================== > Selecting a (/any) plug-in creates white text on a light blue background - an nearly unreadable combination. https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/353 > Does KDE Connect not have a start-with-Windows option? The user expects this. Yes. Please check Task Manager's Startup options. (i.e. it is *not optionally* installed, and can be disabled through the Task Manager) =================================================== > On my grey Windows taskbar, the icon for KDE Connect is hard to see https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/354