https://bugs.kde.org/show_bug.cgi?id=428617
Christoph Feck changed:
What|Removed |Added
Resolution|WAITINGFORINFO |DOWNSTREAM
--- Comment #8 from Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=428617
Thea Barnes changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--- Comment #7 from Thea Barnes ---
(In
https://bugs.kde.org/show_bug.cgi?id=428617
--- Comment #6 from Christoph Feck ---
Please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428617
--- Comment #5 from Thea Barnes ---
(In reply to Mikhail Zolotukhin from comment #4)
> There should be a program called Dr Konqui or something like that on
> Kubuntu. It should show the notification after the crash happened and
> suggest you to show the
https://bugs.kde.org/show_bug.cgi?id=428617
--- Comment #4 from Mikhail Zolotukhin ---
There should be a program called Dr Konqui or something like that on Kubuntu.
It should show the notification after the crash happened and suggest you to
show the backtrace if you click on it.
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=428617
--- Comment #3 from Thea Barnes ---
(In reply to Mikhail Zolotukhin from comment #1)
> I cannot reproduce. Could you please provide a crash backtrace?
What's the easiest way for me to get a stack trace of the crash?
(In reply to Mikhail Zolotukhin fro
https://bugs.kde.org/show_bug.cgi?id=428617
Mikhail Zolotukhin changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=428617
--- Comment #1 from Mikhail Zolotukhin ---
I cannot reproduce. Could you please provide a crash backtrace?
--
You are receiving this mail because:
You are watching all bug changes.
