Bug 702262

Fixed in upstream git. It now requires at least 10 chars in the comment.

Any idea when this is going to land in F15?

(In reply to comment #2)
> Any idea when this is going to land in F15?

I'm going to release an update for F15 this week.

abrt-2.0.3-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/abrt-2.0.3-1.fc15

Package abrt-2.0.3-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.0.3-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/abrt-2.0.3-1.fc15
then log in and leave karma (feedback).

What is an acceptable comment is not self-evident, but by experiment, it appears that any 10 characters will do.

Accepted: "i don't know"
          "don't know"
          "unknown unknown"
          "not known " (space at end)
          "1234567890"
          "          " (10 spaces)
Rejected: "unknown"
          "not known" (no space at end)
          "123456789"
          "         " (9 spaces)

abrt-2.0.3-1.fc15.x86_64

Cross-reference:
Bug 712508 - offer the user an option to not make a comment.

> What is an acceptable comment is not self-evident, but by experiment, it
> appears that any 10 characters will do.
> 
> Accepted: "i don't know"
>           "don't know"
>           "unknown unknown"
>           "not known " (space at end)
>           "1234567890"
>           "          " (10 spaces)
> Rejected: "unknown"
>           "not known" (no space at end)
>           "123456789"
>           "         " (9 spaces)
> 
> abrt-2.0.3-1.fc15.x86_64

Yes, the logic is just:

if (strlen(comment) > 9) allow_send;(In reply to comment #6)

> 
> Cross-reference:
> Bug 712508 - offer the user an option to not make a comment.

- this will probably make Christoph not-happy again ;)

(In reply to comment #7)
> > Cross-reference:
> > Bug 712508 - offer the user an option to not make a comment.
> 
> - this will probably make Christoph not-happy again ;)

Right. :(
I just commented on that bug. IHMO we need an explicit opt-in that users are willing to provide feedback. No feedback -no reports. Simple as that.

My idea for improving this is:

1. make this dependent on the crash type
- we don't need comments for most of the crashes in python apps

2. make it dependent on selected reporter
 - e.g Kerneloops server don't even store the comment anywhere..

3. add the checkbox from #712508 where it makes sense:
 - combination of 1 + 2: e.g: reporting C/C++ crash to bugzilla
 - reporting kerneloops to BZ
but no checkbox and comment not required
 - reporting crash in python app to bugzilla
 - or reporting kerneloops to kerneloops.org

abrt-2.0.3-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Ist this really fixed? AFAICS it is now mandatory to write at least a comment of 5 characters, but when selecting the information to submit, this information is not checked by default and thus will not be included if people just click through the wizards.

(In reply to comment #11)
> Ist this really fixed? AFAICS it is now mandatory to write at least a comment
> of 5 characters,

I don't know whether it is in this update or in the next, but there will be a checkbox "[ ] I don't know", unselected by default.

> but when selecting the information to submit, this information
> is not checked by default and thus will not be included if people just click through the wizards.

I tried current git and "comment" element (which is the element which holds user's explanation) was selected when I chose to report my test crash to Bugzilla. What is the sequence of your actions which leads to it not being selected?

Frankly speaking I don't know. I just clicked through abrt in F15 and the comment was selected. However most reports I receive do not contain any comments.