SUMMARY The application does not work.When I turn on KDE connect it does not show up in the taskbar. When I try to connect it in the upper part of the screen it shows me if I want to pair the phone. How do I click Accept this window is removed. I know that KDE connect does not have official support on windows 10, but it worked before. SYSTEM:Windows 10
*** Bug 407960 has been marked as a duplicate of this bug. ***
Hi there! Which .exe did you run to fire up KDEConnect? If it is kdeconnect-indicator.exe then it **should** show up in the taskbar with a black coloured icon(TODO white). Also, how did you get the KDEConnect installed in your system? If it was a setup file, could you share the link to it? The notifications (including the one which has the "Accept" button) are busted on the official build of KDEConnect on Windows for now; you will have a better experience after about a couple weeks from now :)
I installed from this source:https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/ After click to kdeconnect-indicator.exe there was no black icon on the taskbar in windows 10.
Can you give official source KDE Connect(.exe) on Windows 10,which works? I do not know if official is what I gave you?
Hallo
We have someone working full-time on improving Windows support and it has recently significantly improved. The improved version will probably not be in the binary factory for awhile because of complicated dependencies. You might want to join our development channel, where new versions get posted as they are being worked on: https://community.kde.org/KDEConnect#Development . For now, I have put the latest development version up here: http://172.245.92.84/kde/kde-connect.exe, but don't save this link because I won't be updating it.
*** Bug 408449 has been marked as a duplicate of this bug. ***
It seems that kdeconnect-indicator.exe does not launch kdeconnectd.exe. If first launch kdeconnectd.exe manually and then kdeconnect-indicator.exe, KDE Connect works properly, but there will always be kdeconnectd.exe console window.
(In reply to valdikss from comment #8) > It seems that kdeconnect-indicator.exe does not launch kdeconnectd.exe. If > first launch kdeconnectd.exe manually and then kdeconnect-indicator.exe, KDE > Connect works properly, but there will always be kdeconnectd.exe console > window. could you please check again? indicator does start kdeconnectd.exe in the background for me.
please get the latest build from https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/ or if you're building KDE Connect yourself, please pull the latest changes and build again :)
(In reply to brute4s99 from comment #10) > please get the latest build from > https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/ > > or if you're building KDE Connect yourself, please pull the latest changes > and build again :) Did you change anything in build #88? I tried build #87 yesterday, there was this issue.
I also has this bug. Windows 10 1909 KDE connect nightly 348, 2020-03-27 I worked around this bug with a vbscript. Save the following as startKdeConnect.vbs and place or shurtcut it to the startup folder: Set Shell = CreateObject("WScript.Shell") Shell.Run "taskkill /f /im kdeconnect-indicator.exe", , True Shell.Run """C:\Program Files\KDE Connect\bin\kdeconnectd.exe""", 0, False wscript.sleep (5000) Shell.Run """C:\Program Files\KDE Connect\bin\kdeconnect-indicator.exe""", 0, False
This may be an old issue describing previous problems, but I'm still having trouble pairing Windows 10 with my Android. The script above did little to alleviate this problem. Both devices see and can request pairing with eachother. After accepting on either device kdeconnectd.exe crashes with error code -1073740791. kdeconnect-indicator.exe and dbus-daemon.exe remain running. D:\Program Files\KDE Connect\bin>kdeconnectd.exe kdeconnect.core: Warning: KDE Connect private key file has too open permissions "C:/Users/username/AppData/Local/kdeconnect/privateKey.pem" kdeconnect.core: Warning: KDE Connect certificate file has too open permissions "C:/Users/username/AppData/Local/kdeconnect/certificate.pem" kdeconnect.core: Could not query capabilities from notifications server Accept D:\Program Files\KDE Connect\bin>echo %errorlevel% -1073740791 The first three lines show directly after launching, while "Accept" appears after accepting a pairing request and kdeconnect crashes straight away. If there are any other logs that will be helpful in tracking down this bug please let me know and I will share those. I've tested the latest nightly build on the binary factory (#515), as well as some builds a few months earlier (around april I think) but don't know the version or build number.
(In reply to xfdanpojajauwpuffs from comment #13) > I've tested the latest nightly build on the binary factory (#515), as well > as some builds a few months earlier (around april I think) but don't know > the version or build number. Could you try disabling the notifications plugin? Since the desktop crashes straight away, you might need to do it from your phone. We have some issues with the notifications backend on Windows which are proving difficult to resolve.
I am having a bit more success with build #530, it is largely working but I did notice several different issues I have opened bugs for. (In reply to Simon Redman from comment #14) > Could you try disabling the notifications plugin? I noticed that the Battery monitor plugin will crash KDE Connect during pairing. After having crashed and after restarting KDE Connect, it's made apparent that the pairing was accepted right before the crash. The battery monitor plugin itself is working as expected. All other plugins including the suggested notification plugins can be enabled and pose no problems with pairing. Not sure if this issue was present on build #515? I was entirely unable to pair devices on that build, so there was at least another issue present on that build that has been fixed since. To be exact, KDE Connectd.exe and dbus-daemon.exe both crash, while KDE Connect-indicator.exe remains running with the window becoming unresponsive.
Hi everyone! There has been some improvements on the stability side of things in the Windows port over the past couple of weeks. The battery plugin issue has been resolved as well. Please head to binary factory[1] to try out the new, much more stable build! References:- [1] -> https://binary-factory.kde.org/job/kdeconnect-kde_Nightly_win64/
are there any issues left regarding this bug?