https://bugs.documentfoundation.org/show_bug.cgi?id=169065
Buovjaga <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ilmari.lauhakangas@libreoff | |ice.org --- Comment #2 from Buovjaga <[email protected]> --- You could use the debuginfod service probably supported by Ubuntu to take a backtrace of the hang: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace With debuginfod, the debug information is fetched over the network on demand and there is no need to worry about installing any extra packages. When the debugger starts, it will ask you, if you agree to use the service. Your version of Ubuntu should be automatically configured to use debuginfod: https://documentation.ubuntu.com/server/explanation/debugging/about-debuginfod/ Another, longer, way to initiate the backtrace process is by launching LibreOffice first and then in a terminal running: gdb --pid=$(pidof soffice.bin) At this point it should ask to enable debuginfod. Then in gdb: set logging enabled on and continue (or just c) and then in LibreOffice, open the database to make it crash. With the crash, gdb shows the prompt and you can say backtrace (or just bt) Now a gdb.txt file should be found in the directory where you invoked gdb. Finally, you can say quit in gdb. -- You are receiving this mail because: You are the assignee for the bug.
