Bug 41702 - FILEOPEN: Lotus Word Pro (.lwp) documents < version 11 not supported in LibO
Summary: FILEOPEN: Lotus Word Pro (.lwp) documents < version 11 not supported in LibO
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.3.4 release
Hardware: x86 (IA32) Windows (All)
: medium major
Assignee: Not Assigned
: 45633 130394 (view as bug list)
Depends on:
Blocks: LWP
  Show dependency treegraph
Reported: 2011-10-11 16:36 UTC by Uwe Gode
Modified: 2024-02-04 03:14 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

One of the Lotus Word Pro documents I used. (27.09 KB, application/vnd.lotus-wordpro)
2011-10-11 16:36 UTC, Uwe Gode

Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Gode 2011-10-11 16:36:25 UTC
Created attachment 52242 [details]
One of the Lotus Word Pro documents I used.

When opening a Lotus Word Pro file in LibO Writer, it opens as an empty document. The filename appears in the title bar, but the display is blank. Problem appears under Windows 7 (64-bit) and Windows XP (32-bit). On a third computer with Windows 7 (32-bit), the file also opened as an empty document immediately after the installation of Libre Office; after a reboot is worked fine. Example-file is attached.
Comment 1 Björn Michaelsen 2011-12-23 12:41:13 UTC Comment hidden (obsolete)
Comment 2 sasha.libreoffice 2012-02-03 08:30:13 UTC
LibO 3.3.4 and 3.6.0 master on Fedora 64 bit hangs (and seriously consumes resources of system)
Comment 3 sasha.libreoffice 2012-02-04 05:30:33 UTC
@ Cedric and Michael
Please, look at this. Writer hangs when opening document
Comment 4 A (Andy) 2013-05-02 19:11:12 UTC
reproducible with LO (Win7 Home, 64bit)
Result: opens an empty page
Comment 5 sasha.libreoffice 2013-05-03 06:31:52 UTC
in 4.0.2 on Fedora (RFR) 64 bit also opens as empty document, not hangs.
Title corrected accordingly
Comment 6 tommy27 2013-08-31 15:52:42 UTC
tested with under Win7 64bit.
the .lwp test file is opened but look empty.

can you confirm that the test file is not empty if opened with other softwares rather than LibO?
Comment 7 tommy27 2013-11-04 21:11:03 UTC
still opened as empty file using Version:
Build ID: 86b79ea1f6afb709f2de8141810a61e4162e3125
TinderBox: Win-x86@42, Branch:master, Time: 2013-11-01_23:37:14
Comment 8 Cédric Bosdonnat 2014-01-20 08:57:36 UTC
Restricted my LibreOffice hacking area
Comment 9 Owen Genat (retired) 2014-07-26 10:11:27 UTC
*** Bug 45633 has been marked as a duplicate of this bug. ***
Comment 10 tommy27 2015-06-24 11:47:15 UTC
@ schreiberinfo@gmx.de

please do not change version to a newer release, as indicated it must be the "earliest version" the bug appeared

also do not change priority withoud entering a valid argumentation

I revert your changes and I tell that issue is still reproducibile with recent LibO 5.1 alpha daily build under Win8.1x64
Comment 11 QA Administrators 2016-09-20 10:11:58 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2019-12-03 13:58:24 UTC Comment hidden (obsolete)
Comment 13 Caolán McNamara 2020-02-03 20:17:48 UTC
document is in file format version 10, but the filter only handles version 11 and above
Comment 14 Caolán McNamara 2020-02-03 20:18:44 UTC
*** Bug 130394 has been marked as a duplicate of this bug. ***
Comment 15 Caolán McNamara 2020-02-03 20:20:10 UTC
contemporary LibreOffice reports that the document failed to open, previous versions would present a blank document without reporting that the import had failed
Comment 16 QA Administrators 2022-02-03 03:38:44 UTC Comment hidden (obsolete)
Comment 17 QA Administrators 2024-02-04 03:14:09 UTC
Dear Uwe Gode,

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