Bug 1187552

Summary:	kdeconnect stopped working
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	David Kerkhof <dutchkind>
Component:	KDE Applications	Assignee:	E-Mail List <opensuse-kde-bugs>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	dutchkind, fabian, fvogt, michael
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description David Kerkhof 2021-06-21 14:30:08 UTC

Since a day or two kdeconnect stopped working, from my phone I cannot see my pc and from my pc I cannot see the phone anymore. I just tried it on the same pc in opensuse Leap that I have as a backup and there it is working as expected.
I tried stopping firewalld but that didn't make any difference, haven't found a way to see any device available in kdeconnect.

Comment 1 Fabian Vogt 2021-06-21 14:41:02 UTC

Most likely boo#1187457, already fixed.

*** This bug has been marked as a duplicate of bug 1187457 ***

Comment 2 David Kerkhof 2021-06-21 15:00:42 UTC

I doubt this fixes it, I already have qca-qt5, qca-qt5-plugins and libqca-qt5-2 installed, the only thing that could be installed still is qt6-xxx

I don't have any warnings, journalctl says kdeconnect service was successfully started, but I can't see any external devices

Comment 3 Fabian Vogt 2021-06-21 15:09:39 UTC

Ok, if those package are installed and you did a relogin afterwards it's indeed something else.

Did you run kdeconnect without having qca-qt5 installed once? If so, it might've saved incomplete data, which confuses it now.

Comment 4 David Kerkhof 2021-06-21 15:13:53 UTC

I didn't install those packages, when I just checked 5 minutes ago I saw they were already installed. And since discovering the problem yesterday I have done a few reboots, removed a paired device to see if I could pair it again, but it has just turned blind

Comment 5 Michael Hamilton 2021-06-21 19:45:13 UTC

(In reply to David Kerkhof from comment #4)
> I didn't install those packages, when I just checked 5 minutes ago I saw
> they were already installed. And since discovering the problem yesterday I
> have done a few reboots, removed a paired device to see if I could pair it
> again, but it has just turned blind

Just as Fabian has hinted, I think some users wound up with corrupt config data and had to also remove their $HOME/.config/kdeconnect/ folder to get things working again.  You could always just move the existing one to kdeconnect.old (probably best done when kdeconnect isn't running).

Comment 6 David Kerkhof 2021-06-22 07:26:48 UTC

I just did that and it works. Stopped kdeconnect, renamed it's config folder. In the mean time there was a system update and after that kdeconnect was running again, so don't know if any new thing was installed that solved it but I assume it was an incompatibility between the old and new certificate system.

Anyway, after this kdeconnect is up and working again, thanks!