On Sun, Jul 16, 2017 at 08:02:18PM +0200, nicolas.patr...@gmail.com wrote:
> Le 16/07/2017 16:04:00, Rene Engelhard a écrit :
>
> > This was a strace of the bash, not of LO..
> > You would have needed -f or -ff...
>
> > But I asked about a backtrace from gdb, not about a strace..
>
> Sorry.
> Here is the strace -f output (nearly 2Mo).
OK; thanks.
> I never used gbd but the binary seems to be
> /usr/lib/libreoffice/program/oosplash, not lowriter that is a shell script.
No, the actual binary is soffice.bin. Yes, lowriter is (as is soffice what
it calls, that one "only" calls soffice.bin) one. That's why you need -f.
> [pid 1905] execve("/usr/lib/libreoffice/program/soffice.bin",
> ["/usr/lib/libreoffice/program/sof"..., "--writer", "--splash-pipe=5"], [/*
> 42 vars */] <unfinished ...>
So here the actual LO gets ran.
[ snip ]
Oh, no. nvidia. Does it also happen with drivers actually in Debian?
(If you had Java enabled, you probably would run in to the Java Stack
clash segfault, so don't remove .config/libreoffice as that would reset
it to Defauls, which would crash.)
Regards,
Rene
