https://bugs.kde.org/show_bug.cgi?id=428254
Justin Zobel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=428254
--- Comment #8 from Christoph Feck ---
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428254
--- Comment #7 from Justin Zobel ---
(In reply to Harald Sitter from comment #6)
> I need a sample backtrace all the same. If I just SEGV my kdeconnectd the
> packages get correctly resolved.
Have you got a guide to doing a backtrace? Pretty new to cod
https://bugs.kde.org/show_bug.cgi?id=428254
--- Comment #6 from Harald Sitter ---
I need a sample backtrace all the same. If I just SEGV my kdeconnectd the
packages get correctly resolved.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428254
--- Comment #5 from Justin Zobel ---
Any really. I've tried searching for debug symbols for a number of things
that crashed. The first one when I reported this was for KDE Connect.
On Fri, 30 Oct 2020, 9:25 pm Harald Sitter,
wrote:
> https://bugs.kde
https://bugs.kde.org/show_bug.cgi?id=428254
Harald Sitter changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Assignee|fa...@kde.org
https://bugs.kde.org/show_bug.cgi?id=428254
Justin changed:
What|Removed |Added
Component|Packages User Edition |Packages Unstable Edition
--- Comment #2 from Justin
https://bugs.kde.org/show_bug.cgi?id=428254
--- Comment #1 from Jonathan Riddell ---
The package it wants is kdeconnect-dbgsym but I don't know how kcrash works
that out
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428254
Nate Graham changed:
What|Removed |Added
Product|frameworks-kcrash |neon
Component|general
