[drkonqi] [Bug 315032] KDE crash handling auto-bug-reporting is intimidating and counter productive

Jekyll Wu adaptee at gmail.com
Wed Feb 13 14:44:33 GMT 2013


https://bugs.kde.org/show_bug.cgi?id=315032

Jekyll Wu <adaptee at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kiagiadakis.george at gmail.co
                   |                            |m
          Component|general                     |general
            Version|Git                         |2.1.5
            Product|kde                         |drkonqi

--- Comment #2 from Jekyll Wu <adaptee at gmail.com> ---
(In reply to comment #0)

> 1) The information isn't simply filed somewhere for later analyse, it's used
> (apparently) to generate a full-fledged bug report.  I guess you don't
> expect many users to use it.  However;

I don't know whether that expectation is right , but *the reality* is many
users use DrKonqi to report crashes.  From 2012-01-01 to now, bugs.kde.org
receives about 9K crash reports from users through DrKonqi.   bugs.kde.org
never worries about not receiving enough crash reports. Never.


> 2) The report requires a log in.  I happen to have one, of course I can't
> remember either the user id or the password, so I'm not very likely to do
> anything other than cancel the whole process, but I did actually go to the
> trouble of rediscovering it, and logging in (this had already taken too
> long), whereupon;

Bugzilla  itself (used by bugs.kde.org) requires registered account and login.
That will not change until bugs.kde.org uses a different bug tracker or DrKonqi
doesn't forward crashes to bugs.kde.org anymore. Neither are likely to happen
in the near future.

> 3) You present me with a whole load of bug reports which I'm meant to review
> (I guess nepomukservices crashes a whole load of times.)  Gee.  There's a
> symbol in there at the top of the stack but;

You don't have to . 

> 4) Guess what, I'm not doing that.  If I had that amount of time to spend
> I'd simply debug the crash  myself.  In other words it would take me longer
> to *report* the bug than to fix it.

Fair enough.  Nobody forces you to report it. Actually, the very first dialog
of DrKonqi says it clearly " It is safe to close this dialog if you do not want
to report this bug "

And after you fix it, do not forget to submit a patch at reviewboard.kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list