| Summary: | Device pairings are lost between reboots | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Tamás Barta <tamas> |
| Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | bugseforuns, fabianroeling, nicolas.fella, panderohit, reuben_p, tromzy |
| Priority: | NOR | ||
| Version First Reported In: | 1.8 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | trusted_devices | ||
|
Description
Tamás Barta
2018-06-22 14:27:43 UTC
Just to be sure, your are talking about rebooting the desktop? Does this happen with all your devices? The pairing is stored in ~/.config/kdeconnect/trusted_devices Can you please compare its content before and after reboot? Also please provide your KDE Connect version, distro version and KDE Frameworks version It happens here too, I have to pair my device every time I start my Plasma session. Plasma 5.13, Arch Linux, Frameworks 5.47, KDE Connect 1.3.1. Created attachment 113583 [details]
trusted_devices
This is my file after successful pairing. Before pairing this file is completely empty.
Versions same as above: Plasma 5.13, Arch Linux, Frameworks 5.47, KDE Connect 1.3.1. 5.13.2 just came out, could it fix this issue? I cannot reproduce it anymore, and the file's contents remain between sessions. Can you still reproduce, Tromzy? Sorry, I was too soon to comment. After another login, the file is erased again. I found https://bugs.kde.org/show_bug.cgi?id=368812 Is it possible, that they are related? Same issue here. One way to replicate this is to 'Refresh' the devices on the KDE Connect System Setting Module. The details of my phone are automatically deleted in the trusted_devices file. Is there some way to make it permanent in trusted_devices? Can you try this: - Stop the kdeconnect daemon (killall kdeconnectd, you might want to run this a couple times, to make sure it doesn't self-restart). - Erase kdeconnect's config (the enitire ~/.config/kdeconnect directory) - Start kdeconnectd again from the terminal, and send us the terminal output. Depending on your distro, the path for kdeconnectd might change. Check where it is installed for you. Thank you for your response, Albert. The distro is Arch and the output after following the steps above and restarting the daemon can be seen here: https://pastebin.com/r3ckZZdc I finally figured that the bug lies in the latest Android app rather than the desktop app. The 1.8 version of the app displays this bug and also does not send notifications to the desktop. Downgrading the Android app to version 1.6.6 resolves this. Can confirm. I use KDE Connect 1.18.1 on Android 6 and I need to reconnect my phone after rebooting my laptop running neon unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Graphics Platform: Wayland I still have this issue. Does version 1.6.6 still work with the latest KDE suite versions on desktop? If yes, where I can I find an APK for it? |