Bug 129090 - FILEOPEN: Images missing in imported MS Publisher 2007 file on Windows
Summary: FILEOPEN: Images missing in imported MS Publisher 2007 file on Windows
Status: RESOLVED DUPLICATE of bug 122660
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: regression
Depends on:
Reported: 2019-11-28 23:16 UTC by Andrea Giudiceandrea
Modified: 2019-11-29 10:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

sample file (6.13 MB, application/vnd.ms-publisher)
2019-11-29 10:27 UTC, Xisco Faulí

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea Giudiceandrea 2019-11-28 23:16:55 UTC
All images are not visible in any imported MS Publisher 2007 document.

The images were visible using LibreOffice Draw (x64).

Steps to Reproduce:
1. Open TEST.pub from https://drive.google.com/open?id=1XiHUgbMZWex2yx-P2E19TURyiy5isI4k

Actual Results:
Images are not visible:

Expected Results:
Images are visible (with LO Draw

Reproducible: Always

User Profile Reset: Yes

Additional Info:
LibreOffice Draw (x64)
Build ID: a64200df03143b798afd1ec74a12ab50359878ed
Comment 1 Andrea Giudiceandrea 2019-11-29 07:47:37 UTC
S.O. MS Windows 7 Home Premium SP1 64 bit
Comment 2 Xisco Faulí 2019-11-29 10:27:45 UTC
Created attachment 156177 [details]
sample file
Comment 3 Julien Nabet 2019-11-29 10:44:39 UTC
On Win10 with master sources updated today, I could reproduce this.

I noticed this kind of log:
warn:xmloff:14948:14528:xmloff/source/core/xmlerror.cxx:169: An error or a warning has occurred during XML import/export!
Error-Id: 0x10040001
    Flags: 1 WARNING
    Class: 4 API
    Number: 1
    0: Bitmap_0
Exception-Message: IllegalArgumentException in SvxShape::setPropertyValueImpl. Property Type: string Property nWID: 1018 Value Type: string
Comment 4 Xisco Faulí 2019-11-29 10:45:33 UTC
it seems to be a duplicate of bug 122660

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