[RFC] Disable DrKonqi for KWin in stable releases

[Martin Gräßlin]

On Tuesday 30 April 2013 08:55:55 Daniel Nicoletti wrote:
> The crash reports are there normally to help you fix a some bug
> in the code, I know a flood of crash reports is a pain but what's the
> biggest issue in them? I mean is the backtrace useless or the
> description or even too many duplicates?
Over the last year:
* fixed crashes: 36
* invalid crashes: 7
* wontfix: 3
* worksforme: 4
* unmaintained: 6
* downstream: 7
* backtrace: 10
* upstream: 28
* duplicate: 212

Those duplicates are not duplicates of the 36 fixed issues (which are mostly 
in master). They are duplicates of the 28 upstream issues (driver) and lately 
of the downstream issues.
> 
> Aren't you afraid of losing good crash reports?
NO! And even if, I don't care any more. It's a surrender.
> and if Dr Konqui
> could be tweaked to only send only good crash reports would that help?
no, that would require that DrKonqi gains knowledge to recognize a driver 
crash from a normal crash.
> 
> 2013/4/30 Martin Gräßlin <mgraesslin at kde.org>:
> > Hi all,
> > 
> > <tldr>KWin gets too many crash reports, let's disable DrKonqi</tldr>
> > 
> > the latest post-Ubuntu-release crash report flood made me think that all
> > the crashes we get are only causing work. There is no value in it except
> > that we know that KWin once again crashed because Ubuntu is
> > *insertrandominsulthere*. My initial idea was to discuss with Jonathan
> > and Harald whether we could disable crash reporting just on Ubuntu.
> > 
> > But thinking more about it: there is no benefit at all in the crash
> > reports
> > reported against stable packages. It's all upstream or downstream issues.
> > Since January 1st, 132 crash reports were created but only 10 of them have
> > been fixed. Out of these 10 fixed reports only two are for 4.10.0 (with
> > one of them from a Kubuntu dev running pre-alpha of raring) and one is
> > for 4.10.1. All the other reports are for the alphas and betas.
> > 
> > My suggestion is therefore to push the following patch to stable branch
> > and to future stable branches on final tagging day:
> > diff --git a/kwin/main.cpp b/kwin/main.cpp
> > index ed051f8..710c16d 100644
> > --- a/kwin/main.cpp
> > +++ b/kwin/main.cpp
> > @@ -273,6 +273,7 @@ Application::Application()
> > 
> >      connect(&owner, SIGNAL(lostOwnership()), SLOT(lostSelection()));
> >      
> >      KCrash::setEmergencySaveFunction(Application::crashHandler);
> > 
> > +    KCrash::setDrKonqiEnabled(false);
> > 
> >      crashes = args->getOption("crashes").toInt();
> >      if (crashes >= 4) {
> >      
> >          // Something has gone seriously wrong
> > 
> > We would still get the crash reports in master and during beta and RC for
> > which we are interested, but all the junk would be disabled.
> > 
> > The nice side effect would be that it would look like improved quality as
> > normaly a user wouldn't notice a KWin crash. It's a short flicker during
> > which the window decorations got recrated, but that's it. Has there been
> > a crash if nobody is there to notice it?
> > 
> > Opinions? Can somone convince me to not do it?
> > 
> > --
> > Martin Gräßlin
> > _______________________________________________
> > Plasma-devel mailing list
> > Plasma-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/plasma-devel
> 
> --
> Daniel Nicoletti
> 
> KDE Developer - http://dantti.wordpress.com
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel

--
Martin Gräßlin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-testing/attachments/20130430/b28d5d27/attachment.sig>