https://bugs.documentfoundation.org/show_bug.cgi?id=95039
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|WORKSFORME |--- --- Comment #4 from [email protected] --- Okay, sounds good. Well, maybe not. If a bug, even a severe crash bug like this one, cannot be reliably reproduced, is it best just not to report it? For non-reproducible bugs, it seems like it is a waste of the bug-reporter's time to compose a detailed report. I made it a priority to stop my work and file a bug report to help the LibreOffice community. I spent my time writing all the details. I provided the exact steps I took that fixed the issue. To someone more familiar with the LibreOffice code, that info may hold the key to understanding the problem. If this bug is flagged RESOLVED-WORKSFORME, we will never know, because no one will ever read it. The bug is definitely present. I don't think it's in LibreOffice's best interest to mark known bugs as RESOLVED. Marking it as UNCONFIRMED is appropriate, because it has not been confirmed by another party (well, except for everyone at the client's office who lost confidence in LibreOffice as they watched it crash repeatedly). I truly understand that it makes life much easier when a bug can be reliably reproduced, but the most challenging bugs are not like that. -- 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
