On Monday 12 March 2012 19:26:27 Niko Sams wrote: > On Sun, Mar 11, 2012 at 13:57, henry miller <h...@millerfarm.com> wrote: > > Good ideas, if anyone actually implements it. A couple of comments. > > > > Most users are not programmers - they will not know how to recogize > > similear backtraces are the same root cause. Worse I know of many cases > > where I - a programmer - was wrong. > > > > The more automated detection we can do the better. In fact many random > > crashes have been traced down to the same root cause, so we really need > > the > > ability to check the user's config in a distribution specific way. If some > > misconfiguration is found we can ignore the backtrace. > > DrKonqi already detects duplicates, which works pretty good usually. > But there is still room for improvement... *cough* https://bugs.kde.org/report.cgi?x_axis_field=resolution&y_axis_field=&z_axis_field=&query_format=report- table&short_desc_type=allwordssubstr&short_desc=&product=kwin&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=NEEDSINFO&bug_status=VERIFIED&bug_status=CLOSED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&bug_severity=crash&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfield=[Bug+creation]&chfieldvalue=&chfieldfrom=2011-01-01&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap
That's the stats for all crash reports reported against kwin since 01/01/2011 and now. It illustrates nicely one of the major problems of DrKonqui: you can report the duplicates. Of course KWin is the worst case scenario for measuring DrKonqui as we have all those nice driver bugs ;-) Cheers Martin
signature.asc
Description: This is a digitally signed message part.