https://bugs.documentfoundation.org/show_bug.cgi?id=159590
--- Comment #16 from Adalbert Hanßen <[email protected]> --- (In reply to Julien Nabet from comment #15) > We rather need a backtrace here. (see > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux: > _How_to_get_a_backtrace) As this issue just happened one single time and I don't remember exactly the steps I did before the crash happened: Did I understand it right: Prerequisite for making such a backtrace is that I can cause this bug to happen reproducibly. If this is the case, it is worth following the steps in your linked article and hope that the same bug also shows up also when calling in the backtrace mode soffice --backtrace and do the other steps before and after it as in your linked articles. Right? (Fortunately the bug was not so nasty to show up over and over again, so right now it is not the time for it). In the case of the development version (see above), will I have to call soffice, or will it be a varied name specifying the development version? If this is the case: what is the exact name to be called with --backtrace? -- You are receiving this mail because: You are the assignee for the bug.
