Discussion:
Bug#868507: libreoffice-writer: Crash after the last upgrade
Add Reply
Nicolas Patrois
2017-07-16 08:40:01 UTC
Reply
Permalink
Raw Message
Package: libreoffice-writer
Version: 1:5.3.4-4
Severity: important

Dear Maintainer,

LO crashes after the last upgrade:
X-Error: BadMatch (invalid parameter attributes)
Major opcode: 154
Minor opcode: 5
Resource ID: 0x5c00013
Serial No: 227 (227)
These errors are reported asynchronously,
set environment variable SAL_SYNCHRONIZE to 1 to help debugging
Application Error

-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.3.0-1-686-pae (SMP w/3 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libreoffice-writer depends on:
ii libabw-0.1-1 0.1.1-4
ii libc6 2.24-12
ii libe-book-0.1-1 0.1.2-4
ii libetonyek-0.1-1 0.1.6-5
ii libgcc1 1:7.1.0-9
ii libicu57 57.1-6
ii libmwaw-0.3-3 0.3.11-3
ii libodfgen-0.1-1 0.1.6-2
ii libreoffice-base-core 1:5.3.4-4
ii libreoffice-core 1:5.3.4-4
ii librevenge-0.0-0 0.0.4-6
ii libstaroffice-0.0-0 0.0.3-3
ii libstdc++6 7.1.0-9
ii libwpd-0.10-10 0.10.1-5
ii libwpg-0.3-3 0.3.1-3
ii libwps-0.4-4 0.4.6-2
ii libxml2 2.9.4+dfsg1-3
ii uno-libs3 5.3.4-4
ii ure 5.3.4-4
ii zlib1g 1:1.2.8.dfsg-5

Versions of packages libreoffice-writer recommends:
ii libreoffice-math 1:5.3.4-4

Versions of packages libreoffice-writer suggests:
ii default-jre [java6-runtime] 2:1.8-59
ii fonts-crosextra-caladea 20130214-1
ii fonts-crosextra-carlito 20130920-1
ii libreoffice-base 1:5.3.4-4
pn libreoffice-gcj <none>
ii libreoffice-java-common 1:5.3.4-4
ii openjdk-8-jre [java6-runtime] 8u131-b11-2
ii sun-java6-jre [java6-runtime] 6.26-3

Versions of packages libreoffice-core depends on:
ii fontconfig 2.12.3-0.2
ii fonts-opensymbol 2:102.10+LibO5.3.4-4
ii libboost-date-time1.62.0 1.62.0+dfsg-4+b1
ii libc6 2.24-12
ii libcairo2 1.14.10-1
ii libclucene-contribs1v5 2.3.3.4+dfsg-1
ii libclucene-core1v5 2.3.3.4+dfsg-1
ii libcmis-0.5-5v5 0.5.1+git20160603-3+b1
ii libcups2 2.2.4-2
ii libcurl3-gnutls 7.52.1-5
ii libdbus-1-3 1.10.20-1
ii libdbus-glib-1-2 0.108-2
ii libdconf1 0.26.0-2+b1
ii libeot0 0.01-4+b1
ii libepoxy0 1.3.1-3
ii libexpat1 2.2.2-1
ii libexttextcat-2.0-0 3.4.4-2+b1
ii libfontconfig1 2.12.3-0.2
ii libfreetype6 2.8-0.2
ii libgcc1 1:7.1.0-9
ii libgl1-mesa-glx [libgl1] 17.1.4-1
ii libglib2.0-0 2.52.3-1
ii libgltf-0.1-1 0.1.0-2
ii libgraphite2-3 1.3.10-2
ii libharfbuzz-icu0 1.4.2-1
ii libharfbuzz0b 1.4.2-1
ii libhunspell-1.6-0 1.6.1-2
ii libhyphen0 2.8.8-5
ii libice6 2:1.0.9-2
ii libicu57 57.1-6
ii libjpeg62-turbo 1:1.5.1-2
ii liblcms2-2 2.8-4
ii libldap-2.4-2 2.4.44+dfsg-7
ii libmythes-1.2-0 2:1.2.4-3
ii libneon27-gnutls 0.30.2-2
ii libnspr4 2:4.15-1
ii libnss3 2:3.31-1
ii libodfgen-0.1-1 0.1.6-2
ii liborcus-0.12-0 0.12.1-3
ii libpcre3 2:8.39-3
ii libpng16-16 1.6.30-2
ii librdf0 1.0.17-1.1
ii libreoffice-common 1:5.3.4-4
ii librevenge-0.0-0 0.0.4-6
ii libsm6 2:1.2.2-1+b3
ii libstdc++6 7.1.0-9
ii libx11-6 2:1.6.4-3
ii libxext6 2:1.3.3-1+b2
ii libxinerama1 2:1.1.3-1+b3
ii libxml2 2.9.4+dfsg1-3
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.29-2.1
ii uno-libs3 5.3.4-4
ii ure 5.3.4-4
ii zlib1g 1:1.2.8.dfsg-5

Versions of packages libreoffice-core recommends:
ii libpaper-utils 1.1.24+nmu5

-- no debconf information
Rene Engelhard
2017-07-16 09:00:01 UTC
Reply
Permalink
Raw Message
tag 868507 + moreinfo
thanks

Hi,
Post by Nicolas Patrois
Package: libreoffice-writer
Version: 1:5.3.4-4
Severity: important
Dear Maintainer,
You you mean after the 5.2.7->5.3.4-4 update?
Post by Nicolas Patrois
X-Error: BadMatch (invalid parameter attributes)
Major opcode: 154
Minor opcode: 5
Resource ID: 0x5c00013
Serial No: 227 (227)
These errors are reported asynchronously,
set environment variable SAL_SYNCHRONIZE to 1 to help debugging
Application Error
Interesting, I would have assumed it crashing with Java issues (Stack Clash)
directly. Do you have the stack clash security fixes enabled?

When does it crash?

Do you have a backtrace of this crash?
Post by Nicolas Patrois
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Sigh. Any reason you use this obsolee arch instead of amd64 (if you use -pae ways)?

Regards,

Rene
n***@gmail.com
2017-07-16 13:30:01 UTC
Reply
Permalink
Raw Message
Post by Rene Engelhard
You you mean after the 5.2.7->5.3.4-4 update?
Yes.
Post by Rene Engelhard
Interesting, I would have assumed it crashing with Java issues (Stack
Clash) directly. Do you have the stack clash security fixes enabled?
I don’t know.
Post by Rene Engelhard
When does it crash?
On startup.
Post by Rene Engelhard
Do you have a backtrace of this crash?
Here you are.
Post by Rene Engelhard
Sigh. Any reason you use this obsolee arch instead of amd64 (if you use -pae ways)?
Because my Debian was installed since Potato and I still did not installed the 64bit thingies.


nicolas patrois : pts noir asocial
--
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considÚre comme des humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
Rene Engelhard
2017-07-16 14:10:03 UTC
Reply
Permalink
Raw Message
Hi,

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..

Regards,

Rene
Gesendet: Sonntag, 16. Juli 2017 um 15:24 Uhr
Betreff: Re : Bug#868507: libreoffice-writer: Crash after the last upgrade
Post by Rene Engelhard
You you mean after the 5.2.7->5.3.4-4 update?
Yes.
Post by Rene Engelhard
Interesting, I would have assumed it crashing with Java issues (Stack
Clash) directly. Do you have the stack clash security fixes enabled?
I don’t know.
Post by Rene Engelhard
When does it crash?
On startup.
Post by Rene Engelhard
Do you have a backtrace of this crash?
Here you are.
Post by Rene Engelhard
Sigh. Any reason you use this obsolee arch instead of amd64 (if you use -pae ways)?
Because my Debian was installed since Potato and I still did not installed the 64bit thingies.
nicolas patrois : pts noir asocial
--
RÉALISME
M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
Rene Engelhard
2017-07-16 17:30:01 UTC
Reply
Permalink
Raw Message
Hi,
Post by Rene Engelhard
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..
Thinking about it, maybe both would be helpful. But as said, you need -f
for strace.

a i386 stretch somehow doesn't want to install in my virt-manager so I
can't test myself (yet)...

Regards,

Rene
Post by Rene Engelhard
Gesendet: Sonntag, 16. Juli 2017 um 15:24 Uhr
Betreff: Re : Bug#868507: libreoffice-writer: Crash after the last upgrade
Post by Rene Engelhard
You you mean after the 5.2.7->5.3.4-4 update?
Yes.
Post by Rene Engelhard
Interesting, I would have assumed it crashing with Java issues (Stack
Clash) directly. Do you have the stack clash security fixes enabled?
I don’t know.
Post by Rene Engelhard
When does it crash?
On startup.
Post by Rene Engelhard
Do you have a backtrace of this crash?
Here you are.
Post by Rene Engelhard
Sigh. Any reason you use this obsolee arch instead of amd64 (if you use -pae ways)?
Because my Debian was installed since Potato and I still did not installed the 64bit thingies.
nicolas patrois : pts noir asocial
--
RÉALISME
M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
Rene Engelhard
2017-07-16 18:50:01 UTC
Reply
Permalink
Raw Message
Post by Rene Engelhard
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
n***@gmail.com
2017-07-16 19:10:02 UTC
Reply
Permalink
Raw Message
Post by Rene Engelhard
Oh, no. nvidia. Does it also happen with drivers actually in Debian?
I can run minetest fine, that uses the nvidia driver.
Post by Rene Engelhard
(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.)
I don’t know what do you want from gdb.

nicolas patrois : pts noir asocial
--
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
Rene Engelhard
2017-07-16 19:30:01 UTC
Reply
Permalink
Raw Message
Post by n***@gmail.com
Post by Rene Engelhard
Oh, no. nvidia. Does it also happen with drivers actually in Debian?
I can run minetest fine, that uses the nvidia driver.
That was not the question. I simply don't care wether other stuff does work
width it. Every stuff has it's own quirks and LO uses increasingly more
OpenGL and I wouldn't be surprised if that exposes bugs either in LO _and/or_
in the driver(s).
Post by n***@gmail.com
Post by Rene Engelhard
(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.)
I don’t know what do you want from gdb.
Hmm, I could have sworn /usr/share/doc/libreoffice/README.Debian.gz had this.
(Also has some mentioning of nvidia, also that is from a long time.)

Anyways:

https://wiki.documentfoundation.org/Development/How_to_debug
(which is also trivially findable by googling for "libreoffice gdb backtrace")

Regards,

Rene
Rene Engelhard
2017-07-17 05:40:01 UTC
Reply
Permalink
Raw Message
Post by Rene Engelhard
That was not the question. I simply don't care wether other stuff does
work width it. Every stuff has it's own quirks and LO uses increasingly
more OpenGL and I wouldn't be surprised if that exposes bugs either in LO
_and/or_ in the driver(s).
Of course but when there is a conflict between X and the driver, I always saw that games like minetest or Quake crash but not LO, since yesterday maybe.
Post by Rene Engelhard
https://wiki.documentfoundation.org/Development/How_to_debug
(which is also trivially findable by googling for "libreoffice gdb backtrace")
OK; that is pretty unuseful since there is no actual crash. So we need to
stick on the strace...
X-Error: BadMatch (invalid parameter attributes)
Major opcode: 154
Minor opcode: 5
Resource ID: 0x4800019
Serial No: 242 (242)
These errors are reported asynchronously,
set environment variable SAL_SYNCHRONIZE to 1 to help debugging
Application Error
This seems to be the interesting part.
I don’t know if you have enough information.
Did you try without the binary nvidia drivers?

Regards,

Rene
Rene Engelhard
2017-07-17 07:20:02 UTC
Reply
Permalink
Raw Message
Hi,
Post by Rene Engelhard
Post by Nicolas Patrois
X-Error: BadMatch (invalid parameter attributes)
Major opcode: 154
Minor opcode: 5
Resource ID: 0x4800019
Serial No: 242 (242)
These errors are reported asynchronously,
set environment variable SAL_SYNCHRONIZE to 1 to help debugging
Application Error
This seems to be the interesting part.
Post by Nicolas Patrois
I don’t know if you have enough information.
Did you try without the binary nvidia drivers?
Ah, and it makes sense to test 5.4.0 rc2 from experimental since that
one's going to be in sid very soon now (at least when 5.4.0 final is
being released next week).

5.3.x will be basically abandoned once it migrated to testing or 5.4.0
get released, what comes first :)

Regards,

Rene
n***@gmail.com
2017-07-21 12:20:02 UTC
Reply
Permalink
Raw Message
Post by Rene Engelhard
Did you try without the binary nvidia drivers?
I had a bug with libreoffice-gtk3 a long while ago so I uninstalled it.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838596

When I upgraded libreoffice this morning, I just saw that libreoffice-gtk3 was recommended so I installed it back.
Post by Rene Engelhard
lowriter
error
xsltParseStylesheetFile : cannot parse
I/O warning : failed to load external entity ""
error
xsltParseStylesheetFile : cannot parse
error
xsltParseStylesheetFile : cannot parse
I/O warning : failed to load external entity ""
error
xsltParseStylesheetFile : cannot parse

I think that you can close the bug.

nicolas patrois : pts noir asocial
--
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
r***@debian.org
2017-07-21 12:50:02 UTC
Reply
Permalink
Raw Message
Hi,
Post by n***@gmail.com
Post by Rene Engelhard
Did you try without the binary nvidia drivers?
I had a bug with libreoffice-gtk3 a long while ago so I uninstalled it.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838596
When I upgraded libreoffice this morning, I just saw that libreoffice-gtk3 was recommended so I installed it back.
Ah, OK.

Geoff, does installing libreoffice-gtk3 fix it for you, too (assuming you
use a Gtk3-using desktop or export SAL_USE_VCLPLUGIN=gtk3 or
export OOO_FORCE_DESKTOP="gnome")?
Post by n***@gmail.com
Post by Rene Engelhard
lowriter
error
xsltParseStylesheetFile : cannot parse
I/O warning : failed to load external entity ""
error
xsltParseStylesheetFile : cannot parse
error
xsltParseStylesheetFile : cannot parse
I/O warning : failed to load external entity ""
error
xsltParseStylesheetFile : cannot parse
Yeah, those are known since ages:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688487
Post by n***@gmail.com
I think that you can close the bug.
It would have been better if you didn't file it to begin with. And you didn't
eben answer my intial question.. I'll repeat:

Does it also happen without the binary nvidia drivers?

_Then_ I would feel more comfortable just closing it, yeah.

Regards,

Rene
n***@gmail.com
2017-07-21 13:00:03 UTC
Reply
Permalink
Raw Message
Post by r***@debian.org
It would have been better if you didn't file it to begin with. And
Does it also happen without the binary nvidia drivers?
I wouldn’t have filed it if other games crashed too.
I won’t remove libreoffice-gtk3 if it works with it. The solution was in the presence of this recommended package. If LO crashes back when other games crash too, I’ll tell you but I never saw LO crash because of the nVidia driver (I use the long life version) or a conflict with X but I understand that it may happen (you’re the maintainer, after all, not me).
Note that there is no composite mode in my XFCE session.

nicolas patrois : pts noir asocial
--
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
r***@debian.org
2017-07-21 13:10:02 UTC
Reply
Permalink
Raw Message
Hi,
Post by n***@gmail.com
Post by r***@debian.org
It would have been better if you didn't file it to begin with. And
Does it also happen without the binary nvidia drivers?
[...]
Post by n***@gmail.com
I won’t remove libreoffice-gtk3 if it works with it.
I haven't asked to do that.
Post by n***@gmail.com
I wouldn’t have filed it if other games crashed too.
[...]
Post by n***@gmail.com
If LO crashes back when other games crash too, I’ll tell you but I never saw LO crash because of the nVidia drive
(I use the long life version) or a conflict with X but I understand that it may happen
The point why I Cc'ed Geoff in my reply was his comment to this bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868507#69

--- snip ---
Running the dkms nvidia drivers.

I can run libreoffice if I start with --safe-mode and turn off opengl acceleration so at least there's a work-around.
--- snip ---

So is that is true it's definitely a OpenGL-problem. And either a bug in LO or in the nvidia drivers
(or both.)

That's why I ask again and the last time: does it work without the binary nvidia drivers?

Regards,

Rene
n***@gmail.com
2017-07-21 18:10:02 UTC
Reply
Permalink
Raw Message
Post by r***@debian.org
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868507#69
Running the dkms nvidia drivers.
I don’t run the DKMS drivers, I download them from the nVidia web site.
Post by r***@debian.org
I can run libreoffice if I start with --safe-mode and turn off opengl
acceleration so at least there's a work-around.
I don’t use neither OpenCL nor hardware acceleration (but font antialiasing).
Post by r***@debian.org
So is that is true it's definitely a OpenGL-problem. And either a bug
in LO or in the nvidia drivers (or both.)
That's why I ask again and the last time: does it work without the binary nvidia drivers?
No I didn’t.
I’ll try it when I’ll restart my session.

nicolas patrois : pts noir asocial
--
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
Geoff Reidy
2017-07-22 02:30:01 UTC
Reply
Permalink
Raw Message
Post by r***@debian.org
Ah, OK.
Geoff, does installing libreoffice-gtk3 fix it for you, too (assuming you
use a Gtk3-using desktop or export SAL_USE_VCLPLUGIN=gtk3 or
export OOO_FORCE_DESKTOP="gnome")?
If I don't have libreoffice-kde installed (I run kde/plasma) and I
install libreoffice-gtk3 then it starts up ok. In this case I note that
the option to enable hardware acceleration (under "View" -> "Graphics
Output") is greyed out.

Regards,
Geoff

n***@gmail.com
2017-07-17 05:40:01 UTC
Reply
Permalink
Raw Message
Post by Rene Engelhard
That was not the question. I simply don't care wether other stuff does
work width it. Every stuff has it's own quirks and LO uses increasingly
more OpenGL and I wouldn't be surprised if that exposes bugs either in LO
_and/or_ in the driver(s).
Of course but when there is a conflict between X and the driver, I always saw that games like minetest or Quake crash but not LO, since yesterday maybe.
Post by Rene Engelhard
https://wiki.documentfoundation.org/Development/How_to_debug
(which is also trivially findable by googling for "libreoffice gdb backtrace")
soffice --backtrace
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no debugging symbols found)...done.
log will be saved as gdbtrace.log, this will take some time, patience...
X-Error: BadMatch (invalid parameter attributes)
Major opcode: 154
Minor opcode: 5
Resource ID: 0x4800019
Serial No: 242 (242)
These errors are reported asynchronously,
set environment variable SAL_SYNCHRONIZE to 1 to help debugging
Application Error
Post by Rene Engelhard
cat gdbtrace.log
warning: Currently logging to gdbtrace.log. Turn the logging off and on to make the new setting effective.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xaf529b40 (LWP 21621)]
[Thread 0xaf529b40 (LWP 21621) exited]
[Inferior 1 (process 21614) exited with code 01]
/usr/lib/libreoffice/program/gdbtrace:9: Error in sourced command file:
No stack.
Starting program: /usr/lib/libreoffice/program/soffice.bin --writer
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xaf529b40 (LWP 21632)]
[New Thread 0xaeb03b40 (LWP 21633)]
[New Thread 0xae1ffb40 (LWP 21634)]
[New Thread 0xad7ffb40 (LWP 21635)]
[Thread 0xaeb03b40 (LWP 21633) exited]
[Thread 0xad7ffb40 (LWP 21635) exited]
[Thread 0xaf529b40 (LWP 21632) exited]
[Thread 0xaf713340 (LWP 21628) exited]
[Inferior 1 (process 21628) exited with code 01]
No stack.
warning: Currently logging to gdbtrace.log. Turn the logging off and on to make the new setting effective.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xaf529b40 (LWP 10651)]
[New Thread 0xaeb03b40 (LWP 10654)]
[New Thread 0xae1ffb40 (LWP 10655)]
[New Thread 0xad7ffb40 (LWP 10656)]
[Thread 0xaeb03b40 (LWP 10654) exited]
[Thread 0xad7ffb40 (LWP 10656) exited]
[Thread 0xae1ffb40 (LWP 10655) exited]
[Thread 0xaf529b40 (LWP 10651) exited]
[Inferior 1 (process 10607) exited with code 01]
/usr/lib/libreoffice/program/gdbtrace:9: Error in sourced command file:
No stack.
No stack.

I don’t know if you have enough information.

nicolas patrois : pts noir asocial
--
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
Loading...