[drkonqi] [Bug 317884] drkonqi-4.10.1 shows the wrong bug number if two report windows are opened at once

[Jekyll Wu]

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

--- Comment #4 from Jekyll Wu <adaptee at gmail.com> ---
Well, I know the problem that you try to describle in this report :) I just
don't believe it happpens due to drkonqi itself, thus comment #1.

You seem to have some misundersstanding of how drkonqi works, probably
influenced by the fact that two drkonqi show up almost at the same time. So I
will try to explain why I don't believe it's drkonqi's fault.

First, each drkonqi window run in its own process, so the two drkonqi windows
in your case are totally independent. They are unaware of each other.

Second, drkonqi, just like human being users, doesn't know the number for the
new report before submitting the information. it is told, also like human being
users, by the bugzilla server only after the information is submitted. Adding
informatin to existing report is anthing, see next point.

Third, drkonqi by default always creates new report, unless user explictly
tells it "this looks quite like the existing bug 123456, so adding information
to bug 12345 instead of creating a new report." in the "Looking for possible
duplicates" stage. And how does uses tell drkonqi the crash informatin should
be appened to bug number 123456 ?  Two ways:

    a). drkonqi will ask bugzilla server to search for possible duplcates based
upon backtrace ,  then bugzilla server will sent back those possible duplicates
and drkonqi presents them to users and allow them to read, compare and confirm.
Again, those numbers are given by the bugzilla server and drkonqi will happily
append crash information to one existing report that users has chosen and
confirmed as duplicate. Since the two crash backtrace quite unrelated , I
really doubt this is what have happened.

    b). there is one "Manually enter a bug report id" in the duplicates finding
stage. You can manually enter any existing bug number (like 123456 or 317883),
and drkonqi will happily append crash information to that report. Actually,
this is what I think you have done, see comment #1.  You entered 317883, so the
second drkonqi happily did its due work. But I might be wrong.  


So, let's go through the suspected procedure

> 1. First DrKonqi pops up and figures out which number to use for the bug report. (317883)
it just can't figure out that number. It is told by the server only after the
new report has been created.

> 2. Second DrKonqi pops up and figures out which number to use for the bug report (317883)
same as the first drkonqi. 


> 3. I click through one of the DrKonqis to report the bug. It reports to me that the bug was reported as 317883.
OK, that number 317883 is sent back by bugzilla server to the first drkonqi. 
And the second drkonqi knows nothing about that number by itself..


> 4. I click through the other DrKonqi to report the second bug. It reports to me that the bug was reported as 317883. (But it does not tell me that it reused an existing bug report for that.)

As I have said above, drkonqi always creates new report unless users tell it
not to.  I can only think of two explanation for how the thing happend :

    a). you didn't do anything special(meaning drkonqi should create new
report), then drkonqi sent crash informatin and asked bugzilla server to create
a new report, but bugzilla server didn't create a new report.  The server added
the information to some existing report and sent that existing number back. All
the fault went to the misbehaviing bugzilla server. Quite unlikely.

    a). you somehow clicked that "Manually enter a bug report ID" entry,
entered 317883, and eventually told drkonqi to append information to that
report.  Drkonqi did its job as told. Not its fault.


> (My understanding of the steps may be wrong, but what happened is that the second DrKonqi window wrote into the same bug report, when it should have created its own bug report the way every DrKonqi does. Unless the user identifies it as the same bug during the submission. Here I may have said that it's "related to bug 317883", but I definitely did not identify it as a duplicate.)

That sentence "the report of that is under bug 317883." in the comment part
will not make influence .  It won't accidentally trick drkonqi. The decision of
creating or appending is done before that stage.

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