-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mconnect creates and renames files non-stop in ~/.cache/mconnect
#68
Comments
Removing this line seems to fix the issue. I have no idea about the side effects though. mconnect/src/mconnect/device.vala Line 443 in 51b8144
|
i'm seeing this behaviour as well - I wonder if the mobile app changed behaviour to cause this? from poking around the code last night, that seems like a reasonable solution. though the code also seems to love calling |
I think this is because of a change I ended up reverting, here: https://invent.kde.org/network/kdeconnect-android/-/commit/e4743002be768261a4eab288326bcebf11a308aa I just released 1.26.1 with this revert, let me know if it fixes the issue for you :) |
@albertvaka now I'm having to re-pair my machine upon mconnect ( But the present issue (infinite rewrites) is no longer present. Edit: just noticed that bug report should probably have gone to https://github.com/grimpy/mconnect which is the upstream for https://aur.archlinux.org/packages/mconnect-git |
In the Play Store analytics I can see lots of crashes when the app is trying to restore a saved paired device. The errors seem to be because the certificate isn't properly stored. I wonder if the crashes are all coming from mconnect users for some reason specific to this implementation, or if they come from devices that have some particularity that I still don't know. If you could attach the Android logs after pairing and also after the error happens, hopefully we can find something interesting/useful there. |
I am also running into mconnect requesting pairing a lot of times when I unlock the Android phone. This happens in the few recent android app versions (1.26.x). Is that an issue of the android app, or is mconnect simply not supporting some new changes of the android app? |
I'm the maintainer of the KDE Connect Android app. I'm not sure why this is happening to some users. It would be really useful if someone can send me the Android app logs to debug this, ideally from the latest version (1.27.x). |
I just released version 1.27.1, which might (maybe, hopefully) fix the issue with having to pair the devices again and again. Let me know if it works. |
I noticed heavy usage of my drive, caused by mconnect
Sample log:
The text was updated successfully, but these errors were encountered: