<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - scalc startup with backtrace crashed" href="https://bugs.documentfoundation.org/show_bug.cgi?id=108619#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - scalc startup with backtrace crashed" href="https://bugs.documentfoundation.org/show_bug.cgi?id=108619">bug 108619</a> from <a class="email" href="mailto:olivier.tilloy@canonical.com" title="Olivier Tilloy <olivier.tilloy@canonical.com>"> Olivier Tilloy</a> <pre>That specific crash has been reported both on debian (<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303</a>) and ubuntu (<a href="https://launchpad.net/bugs/1702165">https://launchpad.net/bugs/1702165</a>). It started happening with a recent linux kernel update related to stack clash fixes (see <a href="https://launchpad.net/bugs/1699772">https://launchpad.net/bugs/1699772</a>). Subsequent kernel updates appear to have fixed all userspace apps affected by that crash, except for libreoffice on x86, which is still crashing. Libreoffice on x86-64 is fine. I can reliably reproduce the crash in an Ubuntu 17.04 x86 virtual machine by ensuring that java is enabled in libreoffice's advanced options (using the openjdk-8 package), launching base and creating a new database. A full backtrace with debug symbols is available there: <a href="https://launchpadlibrarian.net/326892034/libreoffice-base-zesty-full-backtrace.txt">https://launchpadlibrarian.net/326892034/libreoffice-base-zesty-full-backtrace.txt</a>.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>