Bug 170330 - Libreoffice writer crashes after File - Open document requested
Summary: Libreoffice writer crashes after File - Open document requested
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-13 17:28 UTC by vymazal
Modified: 2026-01-23 20:33 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
libreoffice writer crash (11.02 KB, text/plain)
2026-01-14 18:42 UTC, vymazal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vymazal 2026-01-13 17:28:43 UTC
Description:
Libreoffice writer crashes after File - Open document requested


Steps to Reproduce:
1.From console type: libreoffice --writer
2.From File menu go to Open File
3.This is the result 
~$ libreoffice --writer
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Unspecified Application Error


Actual Results:
~$ libreoffice --writer
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Unspecified Application Error

Expected Results:
Open selected file


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.2.7.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 16; OS: Linux 6.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ
Ubuntu package version: 4:24.2.7-0ubuntu0.24.04.4
Calc: threaded

Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.12
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.14.0-37-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 8700F 8-Core Processor
Memory: 61.4 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B840M DS3H
System Version: Default string-CF-ADO
Comment 1 raal 2026-01-13 17:32:58 UTC
Can you try in safe mode (Nouzový režim)?
https://wiki.documentfoundation.org/UserProfile/cs
Comment 2 vymazal 2026-01-14 18:42:54 UTC
Created attachment 205049 [details]
libreoffice writer crash

I can't run the Xserver/Desktop under the same user in recovery mode.

But I run the libreoffice under gdb and result is in the attachment.

~$ gdb /usr/lib/libreoffice/program/soffice.bin
(gdb) catch throw std::bad_alloc​
Catchpoint 1 (throw)
(gdb) run
Starting program: /usr/lib/libreoffice/program/soffice.bin 
[Thread debugging using libthread_db enabled]

.
.
.
.
.
.
Thread 1 "soffice.bin" hit Catchpoint 1 (exception thrown), 0x00007fb8b86bb35a in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6
Comment 3 vymazal 2026-01-20 18:52:16 UTC
Run Libreoffice in safe mode cause the same problem.

BUT, whein I run libreoffice under the root user, libreoffice works normal and is capable to return the directory tree when try to save the file under different name.
Comment 4 vymazal 2026-01-23 20:33:46 UTC
SOLVED

Uninstall all libreoffice .deb packages via apt

    apt list |grep instal|grep libreoffice
    apt remove libreoffice +++all other libreoffice packages
    
    
Install libreoffice via snap

    snap install libreoffice
    
Now, you will have to switch your user temp files to /home/user[id]/temp
otherwise your snap libreoffice will not open attachmenst from another applications (thunderbird etc)
#https://askubuntu.com/questions/1046890/libreoffice-cant-access-tmp-files-in-18-04

Check where is your current temporary directory:
    echo $TMPDIR
or
    mktemp -u
It should something look like: /tmp/tmp.zrBHbp0Yt0


Edit the file /etc/profile
    sudo gedit /etc/profile
    
Append the following code:

if [[ -O /home/$USER/tmp && -d /home/$USER/tmp ]]; then
    TMPDIR=/home/$USER/tmp
    
else
    # You may wish to remove this line, it is there in case
    # a user has put a file 'tmp' in there directory or a
    rm -rf /home/$USER/tmp 2> /dev/null
    mkdir -p /home/$USER/tmp
    TMPDIR=$(mktemp -d /home/$USER/tmp/XXXX)
fi

TMP=$TMPDIR
TEMP=$TMPDIR

export TMPDIR TMP TEMP


Reboot

Check if your temporary directory has been reassigned to your /home/user/ directory

    echo $TMPDIR
    
This time, the return should be something like: /home/user/tmp/nrXo , showing that the temp
directory has been reassigned.