| Summary: | Kdeconnect on Linux crashes, Android app cannot find my laptop | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | zopiroku |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | aleixpol, alexgallotta, bucky, faure, freedomj79, matthijstijink, nate |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | 6495e8dc538610fb679df0f1522243103a3a1789 | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: | crash coredump | ||
|
Description
zopiroku
2018-01-27 16:22:54 UTC
I said on OP that it was taking too long to crash this time, as it usually takes only 2 hours, 3 tops. Well, it crashed again. I have absolutely no idea about any of this, but there are some new things, so in case you need more info, here is the backtrace: https://pastebin.com/raw/TefP2dqp I can see that something happens, but not were this happens. It's hard to debug this without debug symbols. Can you recompile kdeconnect with debug symbols? There's instructions here, https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces, but they may be a bit difficult to follow if you do not have any experience with compiling stuff. Also adding David Faure maintainer, since the crash happens in KIO code. Thanks Matthijs. That's way over my head, but I'll give it a try as soon as I can. Hi again,
I compiled kdeconnect with debug symbols, following the Arch Wiki, but, with no experience on this whatsoever, I'm not sure if I did it correctly.
My /etc/makepkg.conf has this line:
OPTIONS+=(!strip docs !libtool !staticlibs emptydirs zipman purge !optipng !upx debug)
The PKGBUILD I used to compile kdeconnect has this line:
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
After compiling for a few minutes, I got a 45 MB *.pkg.tar (instead of the typical ~500 KB for kdeconnect), which I installed.
I then run:
pkill kdeconnectd
gdb /usr/lib/kdeconnectd
(gdb) run
After which the program works fine (clipboard, ping, some commands I added...).
After some time I get the next message:
Thread 1 "kdeconnectd" received signal SIGSEGV, Segmentation fault.
However, neither "coredumpctl list" nor journalctl show anything. With previous installs, using the packages from the offical repos and without using gdb, there were messages about the segfault.
In any case, kdeconnect on laptop doesn't even show my phone, and the Android app is still "connected" but clearly not working (no clipboard, commands don't work...).
Back to gdb, I run:
set logging file trace.log
set logging on
thread apply all bt full [several Enters to show the whole thing]
set logging off
quit [confirm exit with Y]
I then open the settings on the laptop, refresh, and after a few seconds everything works again.
Here is the commands I wrote and what the terminal showed:
https://pastebin.com/raw/BeBv7S5G
And here is trace.log, which if I'm not mistaken is exactly the same:
https://pastebin.com/raw/1sCLgiGQ
Once it was running again, I re-run gdb again, but this time not with "run", but with "start". It crashed after a few hours, but this time I did get a coredump.
Here is the output of journalctl:
https://pastebin.com/raw/BhvmrSg6
Here is the result of coredumpctl:
https://pastebin.com/raw/rmXtdm5L
Here is the trace.log I got from gdb, very short:
https://pastebin.com/raw/d6NwrFM8
If I made any mistakes, please tell me and I'll try to fix it.
Should be fixed by: https://cgit.kde.org/kdeconnect-kde.git/commit/?id=6495e8dc538610fb679df0f1522243103a3a1789 Hi all, yesterday I upgraded kdeconnect on Android (1.8). Both yesterday and today I got the same problem again: after 2-3 hours it disconnects. Again, uninstalling and installing kdeconnect 1.6.6 fixes the problem. Since the old version is awesome enough, I think I'll stick to it. Created attachment 115534 [details]
crash coredump
I noticed that my coredump is different from the previous. Anyway, it happens only when receive notification plugin is turned on if it can help P.S. this is the coredump when notification receive is on https://pastebin.com/1rKb2WX1 Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Might this be a duplicate of 427560? Dr. Konqi thinks that one matches my backtrace -- so it warned me to ignore the error unless I know for a fact that the information is needed -- but I wasn't using SDDM or logging out. What happened for me in real life was that I got a notification on my phone, and then I got a kdeconnect crash notification on my desktop. I Googled, and got https://bbs.archlinux.org/viewtopic.php?id=238636, which seems to match my experience, and that page referenced this bug. Since the status of /this/ bug is "needsinfo," I thought maybe it would be okay if I said something. I apologize if I really do have nothing of substance to offer. But I thought I'd chance it. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I'm having the same issue here. Now I can't get Connect or SMS to see each other on: Parrot OS 5.0 KDE Framework 5.78.0 Kernel 5.15.2-5parrot1-amd64 OnePlus 8T+ 5G Oxygen Dell Optiplex 7010 Win 10 **H2? None will see each other anymore. |