Bug 368819 - Unable to unpair a previously connected device
Summary: Unable to unpair a previously connected device
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-14 20:44 UTC by Tyler
Modified: 2016-09-19 15:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tyler 2016-09-14 20:44:06 UTC
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.
Comment 1 Tyler 2016-09-14 21:14:02 UTC
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.
Comment 2 Albert Vaca Cintora 2016-09-15 09:43:49 UTC
Unpairing from system settings didn't work?
Comment 3 Tyler 2016-09-15 13:12:09 UTC
(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.
Comment 4 Albert Vaca Cintora 2016-09-19 10:00:43 UTC
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.
Comment 5 Tyler 2016-09-19 15:38:59 UTC
(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.