Bug 160840 - Crash on libuno_sal.so.3 when saving document on DOCX (Word 2007-365)
Summary: Crash on libuno_sal.so.3 when saving document on DOCX (Word 2007-365)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.5.9.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: DOCX
  Show dependency treegraph
 
Reported: 2024-04-27 09:15 UTC by Stas Fomin
Modified: 2026-05-13 03:15 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Document to reproduce the bug and crash stacks for releases 7.5.9.2 and 7.5.2.2 (26.89 KB, application/zip)
2024-04-27 09:15 UTC, Stas Fomin
Details
gdb bt (13.93 KB, text/plain)
2024-04-28 19:34 UTC, Julien Nabet
Details
Stack from safe-mode and 7.5.9.2 (1.57 KB, application/zip)
2024-04-28 19:46 UTC, Stas Fomin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stas Fomin 2024-04-27 09:15:48 UTC
Created attachment 193876 [details]
Document to reproduce the bug and crash stacks for releases 7.5.9.2 and 7.5.2.2

* Unpack attachment cannot-be-saved-as-docx-bug.zip
* Open cannot-be-saved-as-docx-v01.odt
* Try to save as DOCX (Word 2007-365) 
* Got crash with stack-7.5.9.2.txt

...
Fatal exception: Signal 6
Stack:
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3b07c)[0x7f3e4461307c]
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x420f2)[0x7f3e4461a0f2]
/lib64/libc.so.6(+0x3dbb0)[0x7f3e44316bb0]
/lib64/libc.so.6(+0x8e884)[0x7f3e44367884]
/lib64/libc.so.6(gsignal+0x1e)[0x7f3e44316afe]
/lib64/libc.so.6(abort+0xdf)[0x7f3e442ff87f]
/usr/lib64/libreoffice/program/libvcllo.so(+0x337657)[0x7f3e40737657]
/usr/lib64/libreoffice/program/libsofficeapp.so(+0x3ce32)[0x7f3e4452de32]
/usr/lib64/libreoffice/program/libvcllo.so(+0x73922d)[0x7f3e40b3922d]
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x4202a)[0x7f3e4461a02a]
/lib64/libc.so.6(+0x3dbb0)[0x7f3e44316bb0]
/lib64/libc.so.6(+0x8e884)[0x7f3e44367884]
/lib64/libc.so.6(gsignal+0x1e)[0x7f3e44316afe]
/lib64/libc.so.6(abort+0xdf)[0x7f3e442ff87f]
/lib64/libstdc++.so.6(_ZN11__gnu_debug19_Safe_sequence_base12_M_get_mutexEv+0x0)[0x7f3e440df1a0]
/usr/lib64/libreoffice/program/../program/libmswordlo.so(+0xa2997)[0x7f3e112a2997]
/usr/lib64/libreoffice/program/../program/libmswordlo.so(+0x1355b9)[0x7f3e113355b9]
/usr/lib64/libreoffice/program/../program/libmswordlo.so(+0xc4a90)[0x7f3e112c4a90]
/usr/lib64/libreoffice/program/../program/libmswordlo.so(+0x15118d)[0x7f3e1135118d]
/usr/lib64/libreoffice/program/../program/libmswordlo.so(+0xd4465)[0x7f3e112d4465]
/usr/lib64/libreoffice/program/../program/libooxlo.so(_ZN3oox4core10FilterBase6filterERKN3com3sun4star3uno8SequenceINS4_5beans13PropertyValueEEE+0x179)[0x7f3e117a11e9]
/usr/lib64/libreoffice/program/../program/libwriterfilterlo.so(+0x1b14e7)[0x7f3e11db14e7]
...


Tested on releases 7.5.9.2 and 7.5.2.2 (see stack-7.5.2.2.txt) on Fedora (FC38).
Comment 1 m_a_riosv 2024-04-27 22:53:56 UTC
No crash on Windows with:
Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: es-ES
Calc: CL threaded
neither
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

Please test in safe mode, Menu/Help/Restart in Safe Mode
Comment 2 Julien Nabet 2024-04-28 19:34:17 UTC
Created attachment 193883 [details]
gdb bt

On pc Debian x86-64 with master sources updated today, I could reproduce this.
Comment 3 Stas Fomin 2024-04-28 19:46:15 UTC
Created attachment 193884 [details]
Stack from safe-mode and 7.5.9.2

The bug reproduced in safe-mode for 7.5.9.2 on FC38
«libreoffice --norestore  --safe-mode»
Comment 4 QA Administrators 2026-05-13 03:15:10 UTC
Dear Stas Fomin,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug