Bug 111961 - Libreoffice crashes after upgrade from debian jessie to stretch
Summary: Libreoffice crashes after upgrade from debian jessie to stretch
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.7.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: wantBacktrace
Depends on:
Blocks:
 
Reported: 2017-08-22 09:26 UTC by ratrace
Modified: 2017-10-25 10:49 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
backtrace (13.82 KB, text/x-log)
2017-08-22 15:13 UTC, ratrace
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ratrace 2017-08-22 09:26:53 UTC
I upgraded my system from debian jessie to stretch. The first problem, after i completed the procedure, was that i couldn't see the GUI(gnome) but only a command prompt. By using an advice in the link below i managed to start the system and see the GUI (gnome). I'm mentioning that in case that is relevant to the problem.

https://www.linuxquestions.org/questions/linux-newbie-8/how-to-start-gnome-gui-desktop-on-debian-stretch-4175612214/

The other major problem that i have, is that libreoffice is crashing. At first i had stable version 5.2.7.1 and since i couldn't work with this version i installed, from backports, the version 5.4.0.1.

The problem that i have can be reproduced in my system by,

1. Opening libreoffice
2. From menu File - New - Text document
3. Libreoffice crashes.

If i'll try to create a new spreadsheet document, libreoffice doesn't crash.

If i try to open a text document that i already have in my disk, libreoffice crashes before opening it. Libreoffice automatically tries to restart but then crashes again and nothing happens.

The only type of document that i can open without problem is calc documents.

Base documents, also crash libreoffice.

I followed an advice that i found in ask.libreoffice.org and deleted the libreoffice-gtk2 file, but that didn't solve any problem.

https://ask.libreoffice.org/en/question/101663/libreoffice-52-crash-debian-90-solved/

Linux 4.9.0-3-686-pae #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) i686 GNU/Linux
Comment 1 Julien Nabet 2017-08-22 09:48:29 UTC
For the test, could you rename your LO directory profile and give a new try? (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux)

Also, what do you use gtk, gtk3?
Comment 2 ratrace 2017-08-22 10:32:11 UTC
I started libreoffice in safe mode and renamed the user profile directory but the behavior of libreoffice is exactly the same.

I don't know what gtk i use. If it is helpful, the command below,

dpkg -l libgtk* | grep -e '^i' | grep -e 'libgtk-*[0-9]'

gives these results,

ii  libgtk-3-0:i386             3.22.11-1    i386         GTK+ graphical user interface library
ii  libgtk-3-bin                3.22.11-1    i386         programs for the GTK+ graphical user interface library
ii  libgtk-3-common             3.22.11-1    all          common files for the GTK+ graphical user interface library
ii  libgtk2-perl                2:1.2499-1   i386         Perl interface to the 2.x series of the Gimp Toolkit library
ii  libgtk2.0-0:i386            2.24.31-2    i386         GTK+ graphical user interface library
ii  libgtk2.0-bin               2.24.31-2    i386         programs for the GTK+ graphical user interface library
ii  libgtk2.0-cil               2.12.40-2    i386         CLI binding for the GTK+ toolkit 2.12
ii  libgtk2.0-common            2.24.31-2    all          common files for the GTK+ graphical user interface library
ii  libgtk2.0-dev               2.24.31-2    i386         development files for the GTK+ library
Comment 3 Julien Nabet 2017-08-22 11:32:51 UTC
Have you installed any specific fonts? if yes could you disable them temporarily for the test?

Also, would it be possible you attach a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Comment 4 ratrace 2017-08-22 15:13:42 UTC
Created attachment 135734 [details]
backtrace
Comment 5 ratrace 2017-08-22 15:15:36 UTC
I'm attaching the backtrace.

I didn't install any additional fonts, except what the debian system automatically installs. How can i disable the fonts?
Comment 6 Rene Engelhard 2017-08-22 15:18:13 UTC
Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0xa31e2f95 in _expand_stack_to(unsigned char*) () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#0  0xa31e2f95 in _expand_stack_to(unsigned char*) () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#1  0xa31e57a4 in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so

So this is the known kernel bug on i386 affecting Java.
Comment 7 Rene Engelhard 2017-08-22 15:22:42 UTC
the workaround is to install the original stretch kernel (-2, see snapshot.debian.org) or boot with the security fixes basically disabled.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303 and friends. Affected jessie, too, though.

This wouldn't have happened if you used 64bit, too.
Comment 8 fabio 2017-10-15 09:59:18 UTC


(In reply to ratrace from comment #0)
> 
> I followed an advice that i found in ask.libreoffice.org and deleted the
> libreoffice-gtk2 file, but that didn't solve any problem.
> 

Same problem when you install Debian 9 in 32 bits. 
Removing libreoffice-gtk3 solve the problem.

Regards,
Comment 9 ratrace 2017-10-25 10:49:43 UTC
The workaround that is described in the post below, works for my system.

https://ask.libreoffice.org/en/question/120447/libreoffice-base-crashes-on-32bit-linux/?comment=135845#post-id-135845