Bug 438944

Summary:	Cannot pair - no available devices
Product:	[Applications] kdeconnect	Reporter:	BingMyBong <bingmybong>
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED FIXED
Severity:	major	CC:	arnim.laeuger
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description BingMyBong 2021-06-20 10:33:31 UTC

SUMMARY
Since the recent issues with opensuse tumbleweed release re: RSA problem (now fixed) etc, no devices appear in either desktop widget or phone (Android 8.1)

STEPS TO REPRODUCE
1. Login to desktop and phone
2. Attempt to pair

OBSERVED RESULT
No devices identified in order to pair.



EXPECTED RESULT


SOFTWARE/OS VERSIONS
opensuse:tumbleweed:20210616
Qt: 5.15.2 KDE Frameworks: 5.83.0 - KDE Plasma:  5.22.0 - kwin 5.22.0
kmail2 5.17.2 (21.04.2) - akonadiserver 5.17.2 (21.04.2) - Kernel:  5.12.10-1-default 

ADDITIONAL INFORMATION
kdeconnect-cli 21.04.2
kdeconnect on phone 1.17.0

Comment 1 Arnim Laeuger 2021-06-20 13:57:48 UTC

I faced the same issue with the same configuration for current opensuse tumbleweed:
- The desktop application kdeconnect-settings doesn't show any devices on the local net
- Other devices don't show the desktop system running tumbleweed
- These devices show mobile and desktop systems _not_ running tumbleweed

My workaround was:
- stop kdeconnectd (and other related services)
- remove ~/.config/kdeconnect

After restart of kdeconnectd, the folder ~/.config/kdeconnect got created with default content. Device discovery (both directions) is back to normal since then.

Comment 2 BingMyBong 2021-06-20 15:08:06 UTC

(In reply to Arnim Laeuger from comment #1)
> I faced the same issue with the same configuration for current opensuse
> tumbleweed:
> - The desktop application kdeconnect-settings doesn't show any devices on
> the local net
> - Other devices don't show the desktop system running tumbleweed
> - These devices show mobile and desktop systems _not_ running tumbleweed
> 
> My workaround was:
> - stop kdeconnectd (and other related services)
> - remove ~/.config/kdeconnect
> 
> After restart of kdeconnectd, the folder ~/.config/kdeconnect got created
> with default content. Device discovery (both directions) is back to normal
> since then.

Thanks, that did the trick.  Another issue has arisen though.  I have multiple logins on my desktop and i paired with each one and my phone listed the devicename/userid for each, it now just lists my main machine name multiple times - is this new or am i missing something?

Comment 3 Arnim Laeuger 2021-06-20 15:16:13 UTC

(In reply to BingMyBong from comment #2)
> I have
> multiple logins on my desktop and i paired with each one and my phone listed
> the devicename/userid for each, it now just lists my main machine name
> multiple times - is this new or am i missing something?

I don't know whether there's an automatic mechanism to identify accounts on a single machine. But I assume that you can provide different/arbitrary name values in each of the users' ~/.config/kdeconnect/config files.

Never tried that myself though.

Comment 4 BingMyBong 2021-06-20 15:47:11 UTC

(In reply to Arnim Laeuger from comment #3)
> (In reply to BingMyBong from comment #2)
> > I have
> > multiple logins on my desktop and i paired with each one and my phone listed
> > the devicename/userid for each, it now just lists my main machine name
> > multiple times - is this new or am i missing something?
> 
> I don't know whether there's an automatic mechanism to identify accounts on
> a single machine. But I assume that you can provide different/arbitrary name
> values in each of the users' ~/.config/kdeconnect/config files.
> 
> Never tried that myself though.

Its not something i've done before, it just worked that way.  I'll close this as Fixed and open a new one for the names.
thanks for the help