Bug 157959 - Can't export some images from an .odt document
Summary: Can't export some images from an .odt document
Status: RESOLVED DUPLICATE of bug 154300
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-28 16:08 UTC by Tomislav Nakic-Alfirevic
Modified: 2023-10-29 08:39 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
.odt containing 2 images, only one of them being exportable (7.72 MB, application/vnd.oasis.opendocument.text)
2023-10-28 16:09 UTC, Tomislav Nakic-Alfirevic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomislav Nakic-Alfirevic 2023-10-28 16:08:14 UTC
Description:
Observed:
Created an .odt document with images. Right-click on upper image, the context menu includes the "Save" option. Right-click the lower image, there is no "Save" option.

Expected: 
The "Save" option is available for all images.

Workarounds:
Rename .odt to .zip, open .zip using any tool, navigate to the appropriate subdir containing images, copy any image you need. Does not work very well when an .odt contains hundreds or thousands of images, but is usable for up to tens of images.

Note:
I'm not sure why there's a "JPG Options" dialogue when saving a JPG file from an .odt to disk as a separate image. I'd expect the image to be saved in the original format the image was in when it was added to the document.

Steps to Reproduce:
See description.

Actual Results:
See description.

Expected Results:
See description.


Reproducible: Always


User Profile Reset: No

Additional Info:
.
Comment 1 Tomislav Nakic-Alfirevic 2023-10-28 16:09:24 UTC
Created attachment 190467 [details]
.odt containing 2 images, only one of them being exportable
Comment 2 Mike Kaganski 2023-10-29 08:39:45 UTC

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