Bug 39299 - Picture paste from clipboard is imported with the wrong size (Windows)
Summary: Picture paste from clipboard is imported with the wrong size (Windows)
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.3.3 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2011-07-17 02:30 UTC by lambdav
Modified: 2015-06-16 14:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Screenshot showing the image size ratio problem (1.14 MB, image/png)
2012-03-01 06:26 UTC, lambdav

Note You need to log in before you can comment on or make changes to this bug.
Description lambdav 2011-07-17 02:30:43 UTC
Using the clipboard, when copying an image area from MS paint to LibreOffice Writer, the image size is incorrect and is resized to a square. Restoring to the original size do not correct this because it seems to have a bad original size.

The problem do not occur when the clipboard image area comes from Gimp. And Gimp seems to paste image area correctly from MS paint. So the problem come from LibreOffice Writer.

So the current workaround if using Gimp instead of MS paint is not possible: instead of doing [Copy from MS paint, Paste to Writer] I have to do [Copy from MS paint, Paste to Gimp, Copy from Gimp, Paste to Writer].
Comment 1 Björn Michaelsen 2011-12-23 12:29:35 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 2 sasha.libreoffice 2012-03-01 03:32:11 UTC
Thanks for bugreport
Please, verify: in last version of LibreOffice still reproducible?
and which windows used?
Comment 3 lambdav 2012-03-01 06:03:37 UTC
Today, I tried and failed to reproduce the problem with Libre Office 3.3.3. I don't know which specific conditions made the problem to occur. I installed the 3.5 version and still wasn't able to reproduce the problem.

I will comment more on this bug if I encounter the problem again with 3.5 version.
Comment 4 sasha.libreoffice 2012-03-01 06:07:05 UTC
Thanks for attempt to reproduce bug
Comment 5 lambdav 2012-03-01 06:08:02 UTC
Sorry, I just reproduced the problem with version 3.5 using a big image size
(2047x1535 pixels).
Comment 6 lambdav 2012-03-01 06:11:59 UTC
The image is a JPEG opened with MS paint. If I just copy small part, the problem doesn't occur. But if I copy the whole image, the image pasted in LibreOffice has wrong ratio.
Comment 7 lambdav 2012-03-01 06:26:49 UTC
Created attachment 57862 [details]
Screenshot showing the image size ratio problem

The screenshot shows MS paint window with the big image visible behind the Libre Office 3.5 window containing the pasted image with invalid width/height ratio.
Comment 8 lambdav 2012-03-01 06:34:29 UTC
I have been able to reproduce the problem with other big images and I think I have found the problem origin :
- using a big square image (5600x5600), the problem doesn't occur.
- using a rectangular part (5600x3800), the problem occur.

-->> The ratio seems inverted when using clipboard data from MS paint.

Whereas if I use GIMP as intermediate (as described in my first comment) the problem doesn't occur.
Comment 9 sasha.libreoffice 2012-03-01 06:37:23 UTC
Thanks for information
Reproduced in 3.5.0 on Windows XP 32 bit
Steps to reproduce:
0. Start msPaint
1. Change size of picture to width=2000 and hight=1500
2. press Ctrl-A and Ctrl-C
3. start Wtiter
4. press Ctrl-V
5. Notice that now hight is more than width
Comment 10 lambdav 2012-03-01 06:41:38 UTC
For additional information:
Reproduced in 3.5.0 on Windows 7 64 bit
Comment 11 QA Administrators 2015-04-19 03:23:39 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (4.4.1 or later)

   *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
   *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)


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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Comment 12 Gordo 2015-06-16 14:00:54 UTC
Could not reproduce.

Windows Vista 64
Build ID: f784c932ccfd756d01b70b6bb5e09ff62e1b3285

Bug present in