Bug 318769

Summary:	Unhandled error when filing a bug against an inactive version of a software
Product:	[Applications] drkonqi	Reporter:	Amyn Bennamane <amynbe>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	amynbe, mail
Priority:	NOR	Keywords:	junior-jobs, usability
Version First Reported In:	2.1.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Amyn Bennamane 2013-04-23 14:59:54 UTC

When I try to file a bug against an inactive version of a software, drkonqi receives an html page from the bugtracker saying that
"The version value 'xxx' is not active.
Please press Back and try again."
So drkonqi does not submit the bug but does not know the reason why. Message displayed by drkonqi:
Error sending the crash report: /Unknown error/
(Two buttons to "Retry" or "Show the content of the report" are available)

Reproducible: Didn't try

Steps to Reproduce:
1. crash an old version of a kde app (e.g. Calligra Words 2.4.0)
2. follow drkonqi to file a bug report
3.
Actual Results:  
No bug report filed (good), but with few information as to why, ant too late.

Expected Results:  
Drkonqi should tell that the version is too old and that the bug report is useless.
Ideally it should do so before the user fills everything and downloads all debug libs.

P.S: Drkonqi version is difficult to find.

Comment 1 Jekyll Wu 2013-04-23 15:22:07 UTC

Yes, this is a known issue and I have anticipated such reports :)  See  my comment in https://bugs.kde.org/show_bug.cgi?id=315073#c3 .

I'm glad to say your expected behaviour is exactly what I want drkonqi to be :)    I have prepared a working patch, but it still needs some polish before it can get  reviewed and merged into KDE SC 4.11. 

>  P.S: Drkonqi version is difficult to find.

Well, DrKonqi is not expected to be directly run by users, but I agree using the KDE SC version might be a better choice . DrKonqi has stayed in version 2.1.5  for quite a long time, although it has received enough change deserving for a version bump.

Comment 2 Amyn Bennamane 2013-04-23 15:33:28 UTC

Oh, so it is a new behaviour of Bugzilla... I came upon the other bug, but since I did not read the last comment, I thought your patch was actually applied but needed improvement...

Comment 3 Jekyll Wu 2013-08-10 07:46:20 UTC


*** This bug has been marked as a duplicate of bug 315073 ***