Currently DrKonqi doesn't do any check of the version of the crashed application. That is why bugs.kde.org still receives useless crash reports from KDE 4.4 or so (I personally regard any report from older than 4.8.5 as useless at the moment). That is just waste of time, for both reporters and developers/triagers. Now that DrKonqi uses the Product.get API to fetch product information[1], it knows which versions are active and which versions are inactive. So it is doable for DrKonqi to detect users are using some no-longer-supported version and ask users to try new versions instead of reporting the problem. Take the 'amarok' product on bugs.kde.org as a example: 2.5-git inactive 2.5.0 inactive 2.6-git inactive 2.6.0 active 2.7.0 active So when drkonqi detects a crash from amarok-2.5.0, it should inform users they are using one outdated version and prevent them from adding useless report to bugs.kde.org. That method requires developers maintaining version information on bugs.kde.org in a serious way. Every version should be available, and every outdated version should be set as inactive. As a complementary method, DrKonqi can also check the kdelibs version (KDE_VERSION_STRING), since a system with outdated kdelibs almost always implies outdated applications, too. [1] https://reviewboard.kde.org/r/108512 Reproducible: Always
Assign it to myself since I plan to work on it and make it into KDE SC 4.11
Git commit c36a1361aafbca1893452771391c07a3c5996c06 by Jekyll Wu. Committed on 14/02/2013 at 10:08. Pushed by jekyllwu into branch 'master'. Add basic checking for product status, component and version status This comes as the initial preparation for preventing crashes from outdated verions being reported to bugs.kde.org. M +2 -0 drkonqi/bugzillalib.h M +31 -3 drkonqi/productmapping.cpp M +7 -0 drkonqi/productmapping.h http://commits.kde.org/kde-runtime/c36a1361aafbca1893452771391c07a3c5996c06
Created attachment 78600 [details] bugzilla rejects drkonqi good news and bad news :) The good news is with bugs.kde.org upgrading to bugzilla 4.2.5, one upstream fix[1][2] means bugs.kde.org itself from now on will rejects any attempt of creating new report against disabled/inactive versions. DrKonqi is no exception. The screenshot shows what happens when I use konsole 2.7.1 ( that version is both available and disabled in the konsole product) to reproduce and report a crash (that crash has been fixed later, of course). So it can be said, from the point of view of end results, that the aim of this report has been (partially) achieved. There will be no new crash reports from outdated applications, which is really good news to bugs.kde.org which has always receives too many reports. The bad news is, as reflected in the screenshot, that bugzilla change introduces one usability issue for drkonqi: it is too late for users using outdated applications to find out they can't really create the report, after spending time in going through all the steps and providing all the information. I can anticipate there will be some complaints filed against drkonqi from angry users in the coming weeks. So to sum up, drkonqi itself still needs to implement the version checking feature , in order to prevent users using outdated applications from reporting problem as early as possible. Another thing is that bugzilla change only applies to creating new reports, so drkonqi still needs to do version checking itself to prevent users using outdated applications adding information (or noise) to existing reports. [1] http://www.bugzilla.org/releases/4.2.5/release-notes.html [2] https://bugzil.la/840824
*** Bug 318769 has been marked as a duplicate of this bug. ***
https://git.reviewboard.kde.org/r/110687/
*** Bug 333612 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 436549 ***