https://bugs.kde.org/show_bug.cgi?id=388991
--- Comment #8 from David Mattatall ---
WOW I think I figured it out. I got a notification from SLACK on my phone just
before it crashed. Don't know why that would do it, here's the dump!
(gdb) thread apply all bt
Thread 4
https://bugs.kde.org/show_bug.cgi?id=388991
--- Comment #7 from Kai Uwe Broulik ---
We're almost there :) when you receive SIGSEGV then type "thread apply all bt"
and paste the output here
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388991
--- Comment #6 from David Mattatall ---
The images being transferred are podcast artwork for pocketcasts on my android.
No reason that should crash anything, and this was happening previous to me
installing pocket casts (I
https://bugs.kde.org/show_bug.cgi?id=388991
--- Comment #5 from David Mattatall ---
Here is the output
tarting program: /usr/lib64/libexec/kdeconnectd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New
https://bugs.kde.org/show_bug.cgi?id=388991
--- Comment #4 from David Mattatall ---
Ok I've hit run, now it's going.
Lemme know what else I need to do.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388991
--- Comment #3 from David Mattatall ---
gdb /usr/lib64/libexec/kdeconnectd appears not to have started it, I cannot
pair.
Is their a guide I can follow to do this?
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=388991
--- Comment #2 from David Mattatall ---
(In reply to Kai Uwe Broulik from comment #1)
> Can you please run kdeconnectd through gdb and get a backtrace?
Sure, i've invoked
gdb /usr/lib64/libexec/kdeconnectd
What do I do
https://bugs.kde.org/show_bug.cgi?id=388991
Kai Uwe Broulik changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=388991
David Mattatall changed:
What|Removed |Added
Keywords||reproducible
--