https://bugs.kde.org/show_bug.cgi?id=375202
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=375202
--- Comment #6 from Bug Janitor Service ---
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
https://bugs.kde.org/show_bug.cgi?id=375202
Justin Zobel changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=375202
--- Comment #4 from Justin Zobel ---
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
https://bugs.kde.org/show_bug.cgi?id=375202
--- Comment #3 from Christoph Feck ---
If gdb shows its (gdb) prompt again after the crash, please use the "bt"
command to actually show the backtrace, and add it here.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=375202
--- Comment #2 from leo.j...@c3ntro.com ---
(In reply to Christoph Feck from comment #1)
> If this is reproducible, please add the backtrace for the crash. For more
> information, please read
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
https://bugs.kde.org/show_bug.cgi?id=375202
--- Comment #1 from Christoph Feck ---
If this is reproducible, please add the backtrace for the crash. For more
information, please read
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
--