[Libreoffice-bugs] [Bug 126488] New: How shall we react if we encounter a crash report?

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Sat Jul 20 17:07:35 UTC 2019


https://bugs.documentfoundation.org/show_bug.cgi?id=126488

            Bug ID: 126488
           Summary: How shall we react if we encounter a crash report?
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: trivial
          Priority: medium
         Component: Writer
          Assignee: libreoffice-bugs at lists.freedesktop.org
          Reporter: adalbert.hanssen at gmx.de

Created attachment 152887
  --> https://bugs.documentfoundation.org/attachment.cgi?id=152887&action=edit
the window reporting a crash report

I just experienced a LibreOffice Crash. Well, it is a development version, so I
am not too much surprised about bugs and crashes. I have a current productive
version in parallel for work that really matters. 

On the screen appeared this window titled “crash report“:

„Please check the report and if no bug report is connected to the crash report
yet, open a new bug report at bugs.documentfoundation.org. Add detailed
instructions on how to reproduce the crash and then show crash ID into the
crash report field.
Thank you for your help in improving LibreOfficeDev.“

There also a white bar in this message which looks like being meant for
entering something there.
    • Where do I find the crash report? Is it in my filesystem? Where?
    • What exactly shall I check for?
    • Where can I enter the description of what I did before the crash
happened?
    • Where do I find the crash ID?

BTW: I guess, the message is generated from LibreOffice when it is re-started
after the crash and some information from the dump is already available in this
moment. This message should be made a bit more instructive about the
interaction of the user. Would it not be possible to show the type of crash
reason (e.g. lost pointer, violated assertion or whatever can be distinguished
in such a tragic situation). 

To help the user, one might ask him about the number of files open
simultaneously in LO, if there were some with multiple windows among them, give
the user some multiple choice field what he did (leaving a freely editable one)
and other things someone hunting for bugs will be interested in. Possibly
interesting questions associated with it also might be
    • Could your currently open files be restored?
    • Did you notice there significant losses in the reconstructed file(s)?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20190720/e6412381/attachment.html>


More information about the Libreoffice-bugs mailing list