Created attachment 143432 [details]
Example

Regarding the size change, I can reproduce it in

Version: 6.2.0.0.alpha0+
Build ID: c290f692dd28094d41dff686f3faa1c4e14b556e
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded

Version: 5.2.0.0.alpha0+
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.10; Render: default; 

Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e

but not in

Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)

Regarding the quality, I think it's the expected quality for a bitmap

Note missing step after 2: deselect shape. Otherwise the bitmap is pasted to the shape and retains its dimensions.

In Linux 41max, there is a huge number of commits, where nothing happens upon pasting. Looks like it is not bibisectable. I did "git checkout bisect/bad" to checkout the first found bad commit and went backwards with git reset --hard HEAD~1000 (various steps) and it seems before the non-pasting there are good results.

Still in LO 7.1.0.0.alpha0+ (abea0d6647c7f1f7e76c73c26cb80e6a67dc5111) / Ubuntu.

The exact change can't be bibisected, but there are two known states (bibisected using repo bibisect-41max): between the following two commits, pasting as bitmap does nothing. Before the first commit, the normal sized image is pasted, after the second commit the smaller image is pasted.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=a548924aece3dc99b2aa36b5c9b0fa52de9951ae
author		Thomas Arnhold <thomas@arnhold.org>	2013-03-06 02:24:16 +0100
committer	Thomas Arnhold <thomas@arnhold.org>	2013-03-12 16:20:15 +0100

"tempfile: Creating tempfiles in a given folder is not used"

https://cgit.freedesktop.org/libreoffice/core/commit/?id=2098b720dd9cdfef5b214802f0b37f49ad42982c
author		Michael Stahl <mstahl@redhat.com>	2013-03-23 22:44:00 +0100
committer	Michael Stahl <mstahl@redhat.com>	2013-03-23 23:02:56 +0100

"tools: TempFile: create a file in ctor, not a directory"

Dear Telesto,

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

MassPing-UntouchedBug