When saving in AOO4115m2(Build:9813)  -  Rev. 5f13fa0070
Thread 1 (Thread 0x7f09ced20740 (LWP 20581) "soffice"):
#0  0x00007f09cedb2687 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f09cedb26ad in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f09ced6307d in sigsuspend () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x0000564f206b24f0 in ?? ()
#4  0x0000564f206b270a in ?? ()
#5  0x0000564f206b3a67 in ?? ()
#6  0x0000564f206acdf9 in ?? ()
#7  0x0000564f206ad583 in ?? ()
#8  0x0000564f206ac297 in ?? ()
#9  0x0000564f206b43a3 in ?? ()
#10 0x0000564f206aa717 in ?? ()
#11 0x00007f09ced4cca8 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x00007f09ced4cd65 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#13 0x0000564f206aa781 in ?? ()

When loading file in AOO4115m2(Build:9813)  -  Rev. 5f13fa0070
Thread 1 (Thread 0x7f33d0fef740 (LWP 20813) "soffice"):
#0  0x00007f33d1081687 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f33d10816ad in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f33d103207d in sigsuspend () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x000055badd92d4f0 in ?? ()
#4  0x000055badd92d70a in ?? ()
#5  0x000055badd92ea67 in ?? ()
#6  0x000055badd927df9 in ?? ()
#7  0x000055badd928583 in ?? ()
#8  0x000055badd927297 in ?? ()
#9  0x000055badd92f3a3 in ?? ()
#10 0x000055badd925717 in ?? ()
#11 0x00007f33d101bca8 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x00007f33d101bd65 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#13 0x000055badd925781 in ?? ()

Enjoy :)
________________________________
From: Damjan Jovanovic <[email protected]>
Sent: 06 November 2025 15:51
To: [email protected] <[email protected]>
Subject: Re: General Error when saving and opening documents in Writer

On Tue, Nov 4, 2025 at 1:22 AM Dean Webber <[email protected]>
wrote:

> Hi Aivaras,
>
> I could try to troubleshoot the install if there is a verbose output for
> soffice I could be looking at, or a diagnostic tool I could use.


Please try the following.

When the error happens, and that popup window is still open, in a terminal
find the process ID (PID) of OpenOffice, usually by running "ps faxww" and
look for "soffice" there.

Then, using the PID from above:
$ gdb
(gdb) attach PID
(gdb) thread apply all backtrace

and paste the output in an email here. That should help us see where the
error is coming from.

You might need to run gdb as root, if the steps above fail.

Regards
Damjan

Reply via email to