Summary: | Crash - on Windows experimental nightly build | ||
---|---|---|---|
Product: | [Applications] kdeconnect | Reporter: | signupemail |
Component: | common | Assignee: | brute4s99 <piyushaggarwal002> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | piyushaggarwal002 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Screenshot
Screenshot |
Description
signupemail
2020-01-22 01:50:31 UTC
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 |