https://bugs.kde.org/show_bug.cgi?id=389518

            Bug ID: 389518
           Summary: Kdeconnect on Linux crashes, Android app cannot find
                    my laptop
           Product: kdeconnect
           Version: unspecified
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: android-application
          Assignee: albertv...@gmail.com
          Reporter: zopir...@69postix.info
  Target Milestone: ---

Hi folks,

for over a year I've been using Kdeconnect without problems, but since last
week's Android app upgrade, version 1.7.1, kdeconnect on my laptop would crash
every 2-3 hours, or even less.
The Android app shows then the following message: "this device is not connected
/can't find any other device. Make sure it's connected to the same Wifi
network", or something like that. In order to regain connection, I have to open
the settings window on Linux and click on Refresh several times. After a few
seconds, everything works again.
Clicking Refresh on Android, or introducing my laptop's private IP, did
nothing.


I've tried downgrading the Linux package, but to no avail. Uninstalling and
re-installing the Android app did nothing either. However, when I downgraded
the Android app to the previous version (1.6.6) using APKMirror, the error
disappeared until I upgraded it again.

I'm using an up-to-date Antergos, with KDE Plasma 5.11.5, KDE Frameworks
5.42.0, and kdeconnect 1.2.1-1 (the same happens with kdeconnect 1.2-1). 


On Linux, journalctl shows the following message every time the crash happens:

https://pastebin.com/raw/rsie5xPt


Using Arch Wiki's article on core dump and debugging, I've created another two
messages. They're very similar, but all this goes waaaay over my head, so I
give you both of them in case it's useful for you:

Doing "coredumpctl info 1289"

https://pastebin.com/raw/JNVebVQJ


Doing "coredumpctl gdb 1289" and then "bt":

https://pastebin.com/raw/WU2SvkXL



I hope that's enough for you guys to know what's wrong. As said, downgrading
the Android app fixed it for a couple of days. I then upgraded it this morning
to force a crash for this bug report, which happened few minutes later. Oddly
enough, though, it's been several hours now and it hasn't crashed yet again.



Thank you for your work!

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to