I installed the older version (0.8) and then found a way to get 1.0 on my system (YUSS). I ran into a problem when I removed the old version and installed the new. The process went like this Install client on Ubuntu (0.8) Install client on Android Remove client from android Remove client from Ubuntu (0.8) Install client on Ubuntu(1.0) Install client on Android So I go to pair again, and the computer is seeing the phone and says its trusted, the phone sees the computer, but says its not paired. I cannot unpair on the computer to initiate the pairing process again. Reproducible: Always Steps to Reproduce: 1. See above Actual Results: Phone will not send a pair request, computer will not unpair. Ping does not work from the computer either. Expected Results: Unpair, reconnect, win at life I'll figure out where the the software stashes its files and try deleting.
Just FYI, figured out that this is EASILY fixed by deleting the data in /home/<user>/.config/kdeconnect/* NBD. Otherwise there is a bit of minor strangeness, but I'm using on Unity, so I can live with that.
Unpairing from system settings didn't work?
(In reply to Albert Vaca from comment #2) > Unpairing from system settings didn't work? Nope, hitting the unpair button did nothing. I thought it was strange too.
I've found that this can happen if you upgrade KDE Connect in the case where you still have the old version of the daemon running, but you launch the new version of the system settings module. Most buttons won't work because of the version mismatch (especially if you upgrade from a really old version like 0.8), but killing the daemon (ie: kdeconnectd) or just logging out and in again should fix the issue. I don't think this is worth a fix, and, in any case, the fix should probably come from the distro's side by adding a installation script which kills the old daemon when installing a new one.
(In reply to Albert Vaca from comment #4) > I've found that this can happen if you upgrade KDE Connect in the case where > you still have the old version of the daemon running, but you launch the new > version of the system settings module. Most buttons won't work because of > the version mismatch (especially if you upgrade from a really old version > like 0.8), but killing the daemon (ie: kdeconnectd) or just logging out and > in again should fix the issue. I don't think this is worth a fix, and, in > any case, the fix should probably come from the distro's side by adding a > installation script which kills the old daemon when installing a new one. I agree, its not really fix worthy especially since it can be fixed simply by purging the contents of the folder I listed above.