Steps how to reproduce with Version: 22.214.171.124.alpha0+
Build ID: 2e3b0c5d42d60d46cd9f8b8eda9424b095c63418; Windows 6.1:
0. Open attached Sample Document
1. Double click Source spreadsheet above
2. Select A71:G84
3. <cntrl+c> for copy
4. Click at the bottom of the test document so that caret flashes there
5. Menu Edit 'Paste Special → GDI Metafile'
» Inserted object looks similar to spreadseeht source, but size of heading
is much too big, so that heading becomes truncated at left and right 😥
a) Works fine with Version: 126.96.36.199 (x64)
CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard;
Gebietsschema: de-DE (de_DE); Calc: group
b) I am using a copy of an existing user profile, new user profile not yet
c) Enabled: OpenGL, Hardware Acceleration, Anti Aliasing,
d) Same bad result when I 'copy → paste special' to Draw document
e) Same result when I 'copy → paste special' from Sample document in LibO 6.3
to Text document in LibO 188.8.131.52
f) because of (d), (e) I am pretty sure that the problem is in 'copy', not in
g) result of 'Paste Special → bitmap' looks ok.
Created attachment 150895 [details]
Document contains spreadsheet source for tests and comparison copy/paste results LibO 6.0 / LibO 6.3
Bibisected with win32-5.3 to https://gerrit.libreoffice.org/plugins/gitiles/core/+/06f319937187f76ee402d53b3baa78c391c2af19%5E%21/
tdf#90937 Add a set of cell styles to calc
When testing the bug, a quick way to select the range is to click in the name box and paste A71:G84
I am not sure if the bibisect result is correct, so adding bibisect request
Arch Linux 64-bit
Build ID: b9a776837462eeb6d50d0decc42604c0c3008eb1
CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: kf5;
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Built on 11 August 2019
I got the same results with bibisect-linux-64-5.3.
Dear Rainer Bielefeld Retired,
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!
Still the same like 2019-04-20 13:59:58 UTC
with Server Installation of Version: 184.108.40.206.alpha0+ (X86_64)
Build ID: 3bc7cc14706f47d740dfc5715970054922ca470c
CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE; Theme: Automatic (Colibre)
Calc: CL threaded – Special new User Profile for testing