https://bugs.kde.org/show_bug.cgi?id=381659
Andrew Crouthamel changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=381659
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #6 from Andrew
https://bugs.kde.org/show_bug.cgi?id=381659
--- Comment #5 from Christoph Feck ---
Well, if you are willing to recompile the packages with debug enabled, sure,
try it. This requires some experience, though.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=381659
--- Comment #4 from Kamil ---
(In reply to Christoph Feck from comment #3)
> Kamil, do not bother. Your distribution does not offer debug information for
> backtraces. If you can reproduce a crash, you are better sending
https://bugs.kde.org/show_bug.cgi?id=381659
--- Comment #3 from Christoph Feck ---
Kamil, do not bother. Your distribution does not offer debug information for
backtraces. If you can reproduce a crash, you are better sending them from a
different distribution.
--
You are
https://bugs.kde.org/show_bug.cgi?id=381659
--- Comment #2 from Kamil ---
(In reply to Marco Martin from comment #1)
> to be useful it needs to be reproduced with debug symbols installed to
> produce a full backtrace
I'm still a novice Linux user and I'm afraid I
https://bugs.kde.org/show_bug.cgi?id=381659
Marco Martin changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO