← Back to context

Comment by buovjaga

20 hours ago

LibreOffice release builds should offer to send a crash report. Ideally, you should then create a bug report referencing the crash report. Besides that, you can do your own build with debug symbols and get backtraces or debug the program.

At The Document Foundation we are always interested in helping deployments. It is also nice to do writeups for our blog. Let me know, if your organisation needs help: ilmari.lauhakangas@libreoffice.org

I recommend to consider our certification program: https://www.documentfoundation.org/certification-program/

I asked about the Maven artifacts and our release engineer will update them later this week.

> you should then create a bug report referencing the crash report

Reducing friction would be nice here - I don't remember encountering the crash log screen, but if you could file a bug report right from that screen, that'd be perfect. A lot of information can be pre-collected at that stage - precise version, build, OS, architecture, processor type, etc. All that'd be left is the "What I was trying to do", my e-mail, and a checkbox if I agree with the privacy policies and if I want to receive e-mail updates about this bug report.

> you can do your own build with debug symbols

It'd be great if the Document Foundation helped distros to offer libreoffice-*-debug packages for this case - if it's crashing for you, install the debug version and your crash logs will be a lot easier to read.

Why does libreoffice have such an annoying document recovery mechanism that I can't turn off or modify? It takes like three clicks to cancel that process every time I open a new doc