Bug 228225

Summary:	No option to provide additional info on desktop / application state at time of crash
Product:	[Applications] drkonqi	Reporter:	joetotale <thanatos>
Component:	general	Assignee:	Dario Andres <andresbajotierra>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	mail
Priority:	NOR	Keywords:	investigated, triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description joetotale 2010-02-23 19:04:52 UTC

Version:            (using 4.4.00 (KDE 4.4.0), Mandriva Linux release 2010.0 (Official) for x86_64)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31.12-desktop-1mnb

When KDE apps crash, the Dr Konqi wizard starts and gathers info on crash.  First page is called "What do you know about the crash?" and asks "Do you remember what you were doing prior to the crash".  I select yes.  I select "Application crashes ever time" and confirm I can report "what I was doing at the time kmail crashed".
Dr Konqi doesn't provide an opportunity for me to enter any further info.
Clicking "show contents of the report"

"...
-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

 -- Backtrace: ..."

Should Dr Konqi allow me to provide such free text?  If I'm meant to save the report and later add a description, should this be explained?

Regards, J

Comment 1 Dario Andres 2010-02-23 19:14:55 UTC

The user can add all the information if the provided crash information is good enough, and the crashed application is a KDE one (and supported in bugs.kde.org). If this two requirements are met, the user can continue reporting the bug (logging into bugs.kde.org; searching for duplicates) and finally adding the information..

I should assume your crash didn't met those requirements

I could try to explain that, or add some hint message like "This information is going to be requested later"

- What do you thing ? 

Regards

Comment 2 Dario Andres 2010-03-17 13:18:00 UTC

Any ideas ?

Comment 3 Dario Andres 2010-12-19 16:04:34 UTC

[Comment from a bug triager]
Waiting for feedback from the reporter

Comment 4 Andrew Crouthamel 2018-09-20 22:06:38 UTC

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 bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Andrew Crouthamel 2018-10-21 04:22:22 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!