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

Christian joulupukin.tontut at yandex.ru
Sat Apr 6 19:36:58 BST 2013


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

--- Comment #3 from Christian <joulupukin.tontut at yandex.ru> ---
OK, I see, the two DrKonqis put the both bug reports into the same bug at bug
317883.
The bug that I am reporting here (bug 317884) is that two DrKonqi bug report
windows (that popped up very shortly after each other) have shared the bug
number. Twice I went through the process of describing the bug, looking at
duplicates, and submitting the bug. (Because there were two crash traces etc.)
This should result in two independent bug reports, irrespective of the fact
that the two windows with the Crash information had popped up at more or less
the same time.
Instead, what happened seems to be:
1. First DrKonqi pops up and figures out which number to use for the bug
report. (317883)
2. Second DrKonqi pops up and figures out which number to use for the bug
report (317883)
3. I click through one of the DrKonqis to report the bug. It reports to me that
the bug was reported as 317883.
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.)

In my view, the bug is in step 2. The second DrKonqi should not pick the same
bug number as the first DrKonqi, because then it cannot report a second bug
that's independent of the first bug.

The bug number should be generated at the end of the submission step, just
before submitting it, and the correct bug number should be shown on the final
"Summary screen".

(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.)

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



More information about the Unassigned-bugs mailing list