Bug 168202 - can't open Libreoffice writer or draw in version 25. Can only open in version 24.8
Summary: can't open Libreoffice writer or draw in version 25. Can only open in versio...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
25.8.1.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-30 19:39 UTC by jabelonger
Modified: 2025-08-31 06:34 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jabelonger 2025-08-30 19:39:45 UTC 
Description:
I can't open any libreoffice files in the latest version 25.8!  This is unacceptable!  They were created in version 24.8.1.  I had to go back to version 24.8.1 to be able to open them.  And I see that 24.8.1 is unsupported come Nov. 2025!!!  Then what?  I hope it's fixed.

Steps to Reproduce:
1. I HAVE to be able to open libreoffice files in the latest version - and I cannot!
2.
3.

Actual Results:
click on libredraw or writer file and nothing happens - won't open.  had do delete latest 25.8 version of Libreoffice and go back to LibreOffice 24.8.1.

Expected Results:
I can only open libreoffice files when I go back to version 24.8.1.   Files will NOT open in 25.8 version of libreoffice.  This is horrible!


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Please fix - this has been an ongoing problem for 5+ months.  It is now 8-30-2025.
Comment 1 jabelonger 2025-08-30 19:40:25 UTC 
Please allow users to open previous versions of libreoffice files in new versions.  It does not work!  Please fix immediately!
Comment 2 m_a_riosv 2025-08-30 20:59:14 UTC 

*** This bug has been marked as a duplicate of bug 168201 ***
Comment 3 Buovjaga 2025-08-31 06:34:20 UTC 
(In reply to m_a_riosv from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 168201 ***

We use rather invalid status for completely identical reports from the same reporter.