[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#933835: libreoffice not start with fatal exception signal 11



tag 933835 + moreinfo
tag 933835 + unreproducible
tag 933835 - a11y
severity 933835 important
thanks

Hi,

On Sun, Aug 04, 2019 at 09:59:51AM +0200, sanskryt wrote:
> Package: libreoffice
> Version: 1:6.3.0~rc2-1
> Severity: grave
> Tags: a11y
> Justification: renders package unusable

No. It isn't a generic problem, and it isn't a11y per se.

> After normal upgradin a system from apt libre office wont start any more.
> Program not start and when put libreoffoce at console there is info:
> 
> sanskryt@sauron:~$ libreoffice
> 
> 
> Fatal exception: Signal 11
> Stack:
> /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bf83)[0x7fc06a40af83]
> /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c193)[0x7fc06a40b193]
> /lib/x86_64-linux-gnu/libc.so.6(+0x37840)[0x7fc06a1e9840]
> /usr/lib/libreoffice/program/libuno_cppu.so.3(+0x14322)[0x7fc06740b322]
> /usr/lib/libreoffice/program/libuno_cppu.so.3(uno_type_any_assign+0x97)[0x7fc06740a717]
> /usr/lib/libreoffice/program/libmergedlo.so(+0x299f047)[0x7fc06cdcb047]
> /usr/lib/libreoffice/program/libmergedlo.so(+0x299fe85)[0x7fc06cdcbe85]
> /usr/lib/libreoffice/program/libmergedlo.so(_ZN3utl10ConfigItemC2ERKN3rtl8OUStringE14ConfigItemMode+0x7b)[0x7fc06cdc104b]
> /usr/lib/libreoffice/program/libmergedlo.so(+0x29f0725)[0x7fc06ce1c725]
> /usr/lib/libreoffice/program/libmergedlo.so(_ZN19SvtSysLocaleOptionsC1Ev+0x11f)[0x7fc06ce1dc1f]
> /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x1a2)[0x7fc06d1ddab2]
> /usr/lib/libreoffice/program/libmergedlo.so(_Z10ImplSVMainv+0x105)[0x7fc06d1df395]
> /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7fc06c28db41]
> /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x555ea9ad007b]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7fc06a1d609b]
> /usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x555ea9ad00ba]

I think I saw this more or less exact backgtrace once when someone using siduction reported
it to me via IRC.

The cause here was siductions live system using overlayfs (and apparmor)

It just works in "normal" systems - verified in clean VM of mine.

Don't use questionable configurations.

Regards,

Rene


Reply to: