Bug 161484 - Image can't be enlarged enough after rotating it / wrong maximum
Summary: Image can't be enlarged enough after rotating it / wrong maximum
Status: RESOLVED DUPLICATE of bug 124498
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Regress-Rotated-Images
  Show dependency treegraph
 
Reported: 2024-06-09 20:56 UTC by markus
Modified: 2024-06-09 23:38 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description markus 2024-06-09 20:56:25 UTC
Description:
After rotating a landscape jpg-image by 90°, it is impossible to enlarge it to full page size of a portrait page by using the green resizing knobs. Instead, the image stays unchanged.

The behaviour is a bit different when i use the properties dialog of the image, but it still does not work.

In my case, it seems that the maximal possible image height is the page width or vice versa. Does maximum calculation ignore rotation?

In practice, this is always relevant whenever someone makes a photo of a document using landscape orientation with the intention to create a portrait pdf.

Steps to Reproduce:
1. create a jpg-picture with the aspect ratio of your libre office writer page, but using landscape.
2. drag that picture into libre offce writer portrait page
3. rotate the landscape picture so that it becomes portrait
4. try to enlarge the picture to full page size

Actual Results:
The picture cannot be enlarged to full page size

Expected Results:
The picture covers the entire page


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Maybe similar to bug 117860, but idk.
Comment 1 Regina Henschel 2024-06-09 23:38:47 UTC
Workaround: Insert the image first in Draw and rotate it there. Then copy it from Draw to Writer.

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