https://bugs.freedesktop.org/show_bug.cgi?id=55379
--- Comment #24 from Markus Mohrhard <[email protected]> --- (In reply to comment #23) > (In reply to comment #22) > > Lets mark this bug as fixed again. Personally I prefer if bug reports are > > not reopened if is not 100% sure that they are related. > > Sorry, but I don’t understand your argument. I did *not* open this bug again > because I think it is related to some other one, but just because Rainer > (comment #15 and #16) and me could still reproduce exactly *this* bug; so > the crash was just not fixed, notwithstanding your patch has fixed an > important problem (thank you very much for that!) ... > > The only possibility I can think of is that, as Rainer suggested, “the > document contains a second crash reason” (comment #16). If this is true, > please state so explicitly, then we can agree that this “second crash > reason” should be handled as bug 55710. Thank you very much! This was a different bug. You can belive me that when I commit a fix for a crash and it still crashes this means that in 99% there is another bug. The second bug was a bit trickier and did not show up in a normal build for me only in a dbgutil build. At least for crashes I think it is a safe assumption that when a develoeprs marks it as fixed and there are still problems around it that opening a new bug report and cc'ing the developer is the better alternative. For example I'm cc'd and assigned to quite a lot of calc bugs and filter more or less all noise that comes from bug reports where I know they are surely fixed. > > > > Normally this bug report should now both being closed as RESOLVED/FIXED and > > as DUPLICATE of Bug 55710. > > Doing both at the same time is impossible ;-) Is this a typo, and did you > mean “and [bug 55633 should be marked] as a DUPLICATE of bug 55710 > [instead]”? Given the possibility mentioned above, this seems a good > solution, and I will do so, in the hope that I understand you correctly. I know that it is not possible which is the problem here. This bug contains now discussions for two bugs with the same symptom but different fixes. My comment was mainly a suggestion to the QA guys who do an amazing job and therefore it is sad if through such problems are hidden behind the normal "noise". If I (and most likely most of the remaining developers ) are set into cc of a bug we at least will have a quick look at the bug report whereas reopening a bug report might go unnoticed if that bug (in the code) is surely gone. Thanks anyway for triaging this bug. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
