Bug 168198 - Crash - Writer 25.8.0.4 crashes after opening a document
Summary: Crash - Writer 25.8.0.4 crashes after opening a document
Status: RESOLVED DUPLICATE of bug 167956
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
25.8.0.4 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-30 17:22 UTC by Thomas S.
Modified: 2025-09-01 08:43 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: https://crashreport.libreoffice.org/stats/crash_details/a925fff0-a977-498e-a249-5bad5ba67213


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas S. 2025-08-30 17:22:21 UTC
Description:
When opening files (.odt or .docx), the file opens and is displayed briefly;
the “Tip of the Day” pop-up appears.
The file is closed and the “File Recovery” window appears.
Error report 250829: https://crashreport.libreoffice.org/stats/crash_details/af117cc3-1eeb-48db-9958-20a2be1b6ba7
Files can be opened in safe mode.

The Writer program can be opened without any problems and new documents can also be saved – the error only occurs when opening documents (regardless of whether from Win Explorer or from Writer).

I've no problems with Impress or Calc.
The problem persists even after completely uninstalling and reinstalling the software.

Steps to Reproduce:
1.Double-click on an .odt or .docx file or open it from LibreWriter, menu “File” > “Open.”
2.
3.

Actual Results:
The file opens and is displayed briefly;
the “Tip of the Day” pop-up appears.
The file is closed and the “File Recovery” window appears

Expected Results:
The file is opened and can be edited.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no (>yes)
Comment 1 Thomas S. 2025-08-30 17:54:50 UTC
The error has been fixed in 25.8.1.1.
Comment 2 Xisco Faulí 2025-09-01 08:43:29 UTC
Thanks for reporting this issue.
This is a duplicated of bug 167956

*** This bug has been marked as a duplicate of bug 167956 ***