Bug 253209

Summary:	Crash report assistant should inform people not to report bugs except against latest stable release
Product:	[Applications] drkonqi	Reporter:	Steve Kroon <kroon>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	adaptee, sitter
Priority:	NOR
Version:	2.1.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=315073
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Steve Kroon 2010-10-04 11:38:37 UTC

Version:           2.9.2 (using KDE 4.5.1) 
OS:                Linux

The crash report assistant should inform people not to report bugs except against latest stable release.  It should tell the user which application crashed, and from which version of which package it comes.  It should refer the user to a place where (s)he can verify that this is the latest stable release.  Alternatively (preferably), this check can be automated if the user has internet connectivity.  [This prevents users wasting their time with debug symbols, etc., only to be told later on freenode's IRC channels not to report the bug since the application is the wrong version.]

Reproducible: Always

Steps to Reproduce:
Crash an app that isn't the latest stable version.

Actual Results:  
You are taken through the crash reporting process for an "out of date" version of the package.

Expected Results:  
User should be told: your software is version x.  However, version y (>x) is the latest stable release, so the crash reporting assistant does not feel it is necessary to report this crash.  To exit.... .  To report anyway, ... .

Comment 1 Jekyll Wu 2013-01-19 02:17:20 UTC

I like the idea.   bugs.kde.org receives too many crash reports from outdated installations, and that is wasting time for reporters, triagers and developers.

One problem, though, is how to identify the outdated versions for different applications.  For application belonging to KDE SC, they are likely to be packaged with the same version of kdelibs, so chekcing the version of kdelibs should be OK. But other applications have different release schedule, and downstream might provide outdated versions for those applications althouth they provide recent KDE SC at the same time.

Comment 2 Jekyll Wu 2013-01-21 01:43:59 UTC

OK, if drkonqi use the Product.get API for fetching product information from bugs.kde.org, then it will know which versions are disabled and not welcoming reports any more. If the version of the crashed application is within those disabled versions, then drkonqi can inform users they are using outdated versions and shouldn't report any bug.   See https://git.reviewboard.kde.org/r/108512/ .

Of course, that depends on developers maintaining version status on bugs.kde.org correctly.

Comment 3 Jekyll Wu 2013-04-03 12:43:34 UTC

See https://bugs.kde.org/show_bug.cgi?id=315073#c3

Comment 4 Harald Sitter 2021-06-21 00:39:22 UTC


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