| Summary: | after every reboot my pairing is gone | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Zamundaaa <xaver.hugl> |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | jestapom, mail, nicolas.fella, reuben_p, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 1.3.3 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
trusted devices after reboot
trusted devices before reboot (so paired) |
||
|
Description
Zamundaaa
2019-01-12 17:30:43 UTC
I tried reinstalling kdeconnect on the PC & also installing the git version using the AUR and reinstalling the app, nothing fixed this. Any further steps I could try? Can you please attach the content of ~/.config/kdeconnect/trusted_devices before and after rebooting? Created attachment 117429 [details]
trusted devices after reboot
Created attachment 117430 [details]
trusted devices before reboot (so paired)
What's also perhaps noteworthy is that it doesn't show my phone in firefox. So it says that I could send this page to my laptop (button greyed out as it's not connected) but doesn't even show my phone at all there So I've now tried removing the trusted devices file, rebooting & pairing again, didn't resolve this either. What's interesting though is that I had kde connect open on my phone and when I logged in on my PC it shortly showed the page like it was paired for less than a second before reverting to the "request pair" page again Another interesting behavior. Today when booting it connected automatically without pairing needed but after I suspended the PC it seemingly revoked the connection again and I had to re-pair I have the same problem since a few weeks or even months. I'm using Arch, so the problem migh be specific for Arch/Manjaro? I've been suffering from this bug aswell ever since I installed Arch some months ago. Possible fix: After cleaning the Android application storage and cache and re-pairing, it works without problem in my case. Haven't had this in a long time now, so I'm marking this as closed. |