Bug 395749 - Device pairings are lost between reboots
Summary: Device pairings are lost between reboots
Status: CONFIRMED
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (other bugs)
Version First Reported In: 1.8
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-22 14:27 UTC by Tamás Barta
Modified: 2025-11-27 18:44 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
trusted_devices (1.14 KB, text/plain)
2018-06-26 17:02 UTC, Tamás Barta
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tamás Barta 2018-06-22 14:27:43 UTC
Every time after a reboot, I have to pair my Android device again. Pairing is solid when using GSConnect, so I don't think this is related to the Android app.
Comment 1 Nicolas Fella 2018-06-23 15:20:37 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
Comment 2 tromzy 2018-06-26 10:19:26 UTC
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.
Comment 3 Tamás Barta 2018-06-26 17:02:15 UTC
Created attachment 113583 [details]
trusted_devices

This is my file after successful pairing. Before pairing this file is completely empty.
Comment 4 Tamás Barta 2018-06-26 17:20:38 UTC
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?
Comment 5 Tamás Barta 2018-06-26 17:28:25 UTC
Sorry, I was too soon to comment. After another login, the file is erased again.
Comment 6 Tamás Barta 2018-06-26 17:29:05 UTC
I found https://bugs.kde.org/show_bug.cgi?id=368812

Is it possible, that they are related?
Comment 7 Rohit Pande 2018-07-28 03:25:36 UTC
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?
Comment 8 Albert Vaca Cintora 2018-07-28 15:44:02 UTC
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.
Comment 9 Rohit Pande 2018-07-29 09:17:56 UTC
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
Comment 10 Rohit Pande 2018-08-16 23:56:55 UTC
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.
Comment 11 Patrick Silva 2021-12-01 23:21:09 UTC
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
Comment 12 Fabian 2025-11-27 18:44:02 UTC
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?