3 ms·
> 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, b
by rbanffy 9mo ago
> 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.
- buovjaga 9mo ago> if you could file a bug report right from that screen, that'd be perfect You can file a bug report from a crash report - it prefills all the relevant data. See an example crash report: https://crashreport.libreoffice.org/stats/crash_details/bac2fbf9-fd3e-4868-8bfb-d323970ddb08 https://crashreport.libreoffice.org/stats/crash_details/bac2... "Bug reports for libc.so.6: File a bug for: Calc Writer Impress Chart Base" Here is what the dialog says about bug reports: https://git.libreoffice.org/core/+/master/svx/uiconfig/ui/crashreportdlg.ui#146 https://git.libreoffice.org/core/+/master/svx/uiconfig/ui/cr... > It'd be great if the Document Foundation helped distros to offer libreoffice-*-debug packages for this case I believe most distros have this covered now, some by making use of debuginfod, which downloads symbols on demand: https://wiki.archlinux.org/title/Debuginfod https://wiki.archlinux.org/title/Debuginfod
- rbanffy 9mo agoThank you. This is all awesome work. BTW, I didn't know debuginfod existed :-)