[drkonqi] [Bug 255037] drkonqi should search for duplicate before asking users to login

[Jekyll Wu]

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

Jekyll Wu <adaptee at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|drkonqi should search for   |drkonqi should search for
                   |application on bugs.kde.org |duplicate before asking
                   |and may ask whether user is |users to login
                   |sure it is a "real" KDE app |

--- Comment #2 from Jekyll Wu <adaptee at gmail.com> ---
A report might be create under the "kde" product for at least two different
reasons:

    1. The application is tracked in bugs.kde.org, but the crashed binary name
doen't match the product name and is not mapped to the correct product.
Examples would be kwin_gles from kwin, muon-installer from muon, etc. 

    2. The application is not tracked in bugs.kde.org, but its author haven't
read the document of KAboutData carefully and set the bug address accordingly.

So a report created under "kde" product doesn't necessarily mean that
application is not tracked here. Even if that is always the case, I also don't
think it would be good idea to ask users to check whether the application is
tracked here. I wouldn't expect average users to know how to correctly check
and answer that question.

And about sending a email to the person specified in aboutData, unfortunately
DrKonqi just can't . DrKonqi run in its separate process, so it can't make use
of the aboutData in another application/process.  It doesn't receive such
information from the command line arguments either.  It just receives the bug
address.

An alternative solution would be drkonqi maintains a list which records common
and well known KDE applications not using bugs.kde.org, and their real tracker
address. When DrKonqi notices the crash is from one such application, it can
inform users to report the crash to the right place and abort the following
procedure.

So change the summary to only reflect the second point.

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