https://bugs.documentfoundation.org/show_bug.cgi?id=152979
--- Comment #10 from Michael Weghorn <[email protected]> --- (In reply to Rafael Lima from comment #8) > Created attachment 186055 [details] > Backtrace > > Here's the backtrace while reproducing the bug. It was created using LO 7.6 > built from master using a clear user profile. Thanks. Could you please install the relevant Qt debug symbols (probably in a package called libqt5core5a-dbgsym or so on Ubuntu) and create + attach another backtrace that hopefully shows more info on where in the Qt library the involved threads are? The GDB log says this at the beginning, so maybe using debuginfod instead of the debug packages might also work if you confirm that in an interactive GDB session (answer the question with "y" instead of the default "n"): > This GDB supports auto-downloading debuginfo from the following URLs: > https://debuginfod.ubuntu.com > Enable debuginfod for this session? (y or [n]) [answered N; input not from > terminal] What I'd try is this: * install debug symbols for /lib/x86_64-linux-gnu/libQt5Core.so.5 (unless this "just works" with debuginfod as alternative) * start LO with GDB from command line: `gdb --args ./instdir/program/soffice.bin --writer` (type "r" to start running the program once the GDB prompt occurs) * reproduce the freeze * in the terminal where GDB runs: press Ctrl+C to pause the execution, then type "thread apply all bt" in the GDB prompt to generate the backtrace for all threads (and attach the result here) -- You are receiving this mail because: You are the assignee for the bug.
