https://bugs.documentfoundation.org/show_bug.cgi?id=144994
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #16 from Michael Weghorn <[email protected]> --- (In reply to giors_00 from comment #14) > I don't know if I did it correctly. Please find attached the gdbtrace.log > file (please confirm if it's ok). Thanks. It turns out that this scenario needs an extra step to get a more useful backtrace, since the JVM (Java Virtual Machine) uses segfaults by itself that are not relevant to the crash discussed here... Anyway, I have set up a VM running arch, and could reproduce the issue there in a Wayland session. It's not 100% reproducible, sometimes crashes, sometimes hangs, sometimes seems to work fine, sometimes runs into an assertion... It seems to be more reprocuible with a release/non-debug build, I've used the current daily build from here: https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@tb87-TDF/current/LibreOfficeDev_7.3.0.0.alpha1_Linux_x86-64_deb.tar.gz Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: 23214f1c14c4d3981dad90b6e3ba6e4ca2c8c30e CPU threads: 2; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Command used: gdb -ex 'handle SIGSEGV nostop' -ex 'r' --args ./opt/libreofficedev7.3/program/soffice.bin --writer --norestore GDB log: ~/gdb.log ----- Also "sometimes" reproducible with a debug build downloaded from here: https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@tb87-TDF-dbg/current/LibreOfficeDev_7.3.0.0.alpha1_Linux_x86-64_archive.tar.gz Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: 23214f1c14c4d3981dad90b6e3ba6e4ca2c8c30e CPU threads: 2; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I'll attach the backtrace for the latter. -- You are receiving this mail because: You are the assignee for the bug.
