Bug 329949

Summary: crash reporter fails with obscure error message after logging in to KDE Bugtracking System
Product: [Applications] drkonqi Reporter: Henk Langeveld <henk>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED WORKSFORME    
Severity: grave CC: mail, sitter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Henk Langeveld 2014-01-14 09:10:56 UTC 
The version value '0.4' is not active.
Please press Back and try again.

Reproducible: Always

Steps to Reproduce:
1. Make something crash (In this case changing height in Panel Settings)
2. Wait for the crash reporter
3. Fill in lots of detail
4. Create a bugs.kde.org account, if necessary
5. Enter credentials
6. Add additional info
7. Submit
8. See it fail
Actual Results:  
The version value '0.4' is not active.
Please press Back and try again.

Expected Results:  
This service should do one of:
1. Fail more gracefully.
2. Supply a hint to alternative ways for reporting errors.
3. Use a different backend (Is BzAPI stable?)
4. Fall back on collecting statistics (just the crash reports, no user interaction, except for approval.)


This is my first experience with KDE after several years.

 A crash reporting service should be a slam/dunk experience.

I'm marking this as Grave, as I feel that the crash reporter in its current state should be disabled until there is a proper backend.
Comment 1 Andrew Crouthamel 2018-11-11 04:22:56 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:27:17 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

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