<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Writer crashes in KDE5 after document reconstruction / at start" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124124#c21">Comment # 21</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Writer crashes in KDE5 after document reconstruction / at start" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124124">bug 124124</a> from <a class="email" href="mailto:m.weghorn@posteo.de" title="Michael Weghorn <m.weghorn@posteo.de>"> Michael Weghorn</a> <pre>(In reply to Sandra Weddig from <a href="show_bug.cgi?id=124124#c20">comment #20</a>) > I did add a new backtrace, one with a different window style and one of the > debug masterbuild (this seems not to run, do I need a different JDK?). Thanks. The easiest workaround is probably to just disable Java by temporarily starting with the gtk3 VCL plugin, i.e. set the environment variable SAL_USE_VCLPLUGIN=gtk3 before starting LibreOffice and then in "Tools" -> "Options" -> "Advanced" disable the checkbox for "Use a Java runtime environment". I've set up an openSUSE Tumbleweed VM for testing and could reproduce the JDK issue, but unfortunately not the crash, which makes this hard to analyse. Looking at the backtrace from <a href="show_bug.cgi?id=124124#c18">comment 18</a> and the involved code, I'd guess that there's a division by zero (causing the "SIGFPE, Arithmetic exception"), possibly because all the variables in the divisor (i.e. "range" and "scrollbar->pageStep") are 0. It would be interesting to have that verified, so it'd be of help if you could start the debug version (with the same widget style as for the backtrace in <a href="show_bug.cgi?id=124124#c19">comment 19</a>) with gdb --args <SOME_PATH>/instdir/program/soffice.bin --writer at which point a '(gdb)' prompt appears. The command 'r' will start the program. If the same crash appears, it'd be good to print the values of the variables involved and the backtrace with these commands then: thread apply all bt p range p scrollbar->pageStep p scrollbar->maximum p scrollbar->minimum and attach the result here. Since this is not really straightforward, please feel free to just leave out those steps and just attach the backtrace. In the meantime, I had the same issue a few times, but couldn't reliable reproduce. Any idea what might help to reproduce this? AFAICS, the relevant values for the 'QStyleOptionSlider option' variable being passed are set at [1] based on values passed to that method by the ImplControlValue param. [1] <a href="https://gerrit.libreoffice.org/plugins/gitiles/core/+/master/vcl/qt5/Qt5Graphics_Controls.cxx#490">https://gerrit.libreoffice.org/plugins/gitiles/core/+/master/vcl/qt5/Qt5Graphics_Controls.cxx#490</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>