Created attachment 147575 [details] Test spreadsheet Text lines are cut and shifted along the former border of the merged cell. The direction and size of the shift are zoom dependent. The used font does not seem to play a role. Test steps: 1. Open attached sample file (or re-create it by merging cells and inputting text) 2. Zoom in or out Expected results: 2. Text letters do not get cut and shifted along their middle Actual results: 2. Text letters get cut and shifted along their middle (corresponding to the former border of merged rows) Note: The text gets "repaired" on update of the cell, e.g., on a change of the used font. But the issue re-appears on subsequent zooming. Reproduced with: Ubuntu 18.04 with LO PPA: Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.2 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (en_US.UTF-8); Calc: group Ubuntu 18.04 liveUSB with LO daily: Version: 6.3.0.0.alpha0+ Build ID: ac7508c31873d79e56b406c9bf931caae63d4975 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2018-12-14_16:04:08 Locale: en-US (C.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 147576 [details] Screenshot showing the issue
Can not reproduce on Windows build 6.1.4.2, or current master. Sounds rather like a GPU driver issue. Please try setting/unsetting the "Use printer metrics for text formatting" checkbox in the Tools -> Options -> LibreOffice Calc -> General panel. We have seen that this will impose better structure on the cells on screen--but at a performance cost when working in the sheet. Let us know if that corrects on screen handling. You might also try updated drivers and a more current build of LibreOffice than 6.0.7 which is EOL.
Created attachment 147580 [details] Screenshot showing the issue, with "use printer metrics..." deactivated Thanks for the quick check! The "Use printer metrics for text formatting" checkbox is unset by default in my case. Unfortunately: - With LO 6.0.7.3 on up-to-date Ubuntu 18.04.1 LTS: Toggling the "Use printer metrics for text formatting" checkbox has no affect. (The cells get re-drawn on the change, resulting in disappearance of the issue, but the issue comes back on the next zoom change.) - With 6.3.0.0.alpha0+ (current daily) on not quite up-to-date Ubuntu 18.04.1 LTS liveUSB: With "Use printer metrics for text formatting" checkbox activated, the issue becomes worse - there is an additional vertical shift of the letter parts. See attached screenshot. It could be a Linux or Ubuntu-specific issue, though. I don't have the combination of the current LO master on fully up-to-date Linux, unfortunately.
Created attachment 147581 [details] Screenshot showing the issue, with "use printer metrics..." activated There was an error in the screenshot naming: it should mean "activated", not "deactivated" (the latter is the default). The image content is the same.
Created attachment 147603 [details] Screenshot showing the issue on Windows I can reproduce the issue on up-to-date 64-bit Windows 10 on the same PC as well, with the current LO portable release 6.1.2: Version: 6.1.2.1 Build-ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: CL So, this might be HW dependent. The PC in question is a notebook with the Intel® Core i5-7200U processor with built-in Intel® HD Graphics 620.
I'll add "Intel HD Graphics" to the title, so far. Johnny, you can use https://libreoffice.soluzioniopen.com/index.php/daily-version/ for testing.
(In reply to Johnny_M from comment #5) What driver release for the Windows 10 build? I have the same Intel 620 GPU on an Intel i7-7500U CPU with the 24.20.100.6229 driver on an 1803 build, and can not reproduce. Also, for the 1809 build of Windows 10 Intel is packaging Universal Windows Driver DCH drivers, currently 25.20.100.6444. So some concern going forward of their behavior on earlier Windows 10 builds.
Thanks for feedback. I got my hands on a a few additional PCs and configurations, all of which show the issue: I) A notebook of the same brand (Fujitsu), but different product line, with Intel Core i7-7500 CPU with built-in Intel HD Graphics 620: 1) With Win10 Pro 1803 (build 17134.472), Intel graphics driver version 21.20.16.4542 of October 24, 2016: LO portable release: Version: 6.1.2.1 Build ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-US (de_DE); Calc: CL II) An ASUS desktop with Intel Core i5-6400 CPU and built-in Intel® HD Graphics 530: 1) With Win10 Home 18.03 (build 17134.472), Intel graphics driver version 22.20.16.4749 of July 24, 2017: Version: 6.1.3.2 (x64) Build-ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: CL 2) With Win10 Home 18.09 (build 17763.195; after search and installation of pending Windows updates), same graphics driver as above: Version: 6.1.4.2 (x64) Build-ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: CL I'm setting the HW platform to "all", since LO portable is 32 bit and is also affected.
(In reply to V Stuart Foote from comment #7) > (In reply to Johnny_M from comment #5) > > What driver release for the Windows 10 build? > > I have the same Intel 620 GPU on an Intel i7-7500U CPU > with the 24.20.100.6229 driver on an 1803 build, and can not reproduce. > > > Also, for the 1809 build of Windows 10 Intel is packaging Universal Windows > Driver DCH drivers, currently 25.20.100.6444. So some concern going forward > of their behavior on earlier Windows 10 builds. P.S. details to comment 5: Win10 Home 1809 (build 17763.194), Intel graphics driver version 24.20.100.6096 of May 23, 2018.
One more PC (here laptop) with Intel graphics showing the issue (I have not yet come across a PC with a non-Intel graphics card so far): Intel Pentium CPU N3520 Win10 Home 18.03 (build 17134.472), Intel graphics driver version 10.18.10.4358 of December 21, 2015 Version: 6.1.4.2 (x64) Build-ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group threaded
A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Still reproducible on the initial machine with current master on Ubuntu MATE 19.10 liveUSB: Version: 6.4.0.0.alpha0+ Build ID: c54597a8905b07807952aebc24237549302fb941 CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-07-10_22:22:02 Locale: en-US (C.UTF-8); UI-Language: en-US Calc: threaded
No problemt at all in Version: 6.5.0.0.alpha0+ Build ID: fc1f85127968d1c2e0a53dace51bf8a78f9e6ca5 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded @Johny, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Created attachment 157419 [details] Screenshot showing the issue on LOdev 7.0 Still reproducible on the initial machine with current master on Ubuntu MATE 19.10 liveUSB: Version: 7.0.0.0.alpha0+ Build ID: 4ff12ba6f4639c73587f2bb58afcc3ca6fb30105 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-01-24_21:09:14 Locale: en-US (C.UTF-8); UI-Language: en-US Calc: threaded Correction to comment 12: Ubuntu 19.04 was used back then, not 19.10.
Confirmed immediately upon opening attachment 147575 [details]. "This is just a check" was displayed as cut & shifted. I have Intel Corporation HD Graphics 530 Arch Linux 64-bit Version: 6.4.3.2 Build ID: 6.4.3-1 CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Arch Linux 64-bit Version: 7.0.0.0.alpha0+ Build ID: 623d6cf06ccba392c1993a3b0ad271d508205e73 CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 29 April 2020
Dear Johnny_M, 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
The issue is no longer reproducible on (same PC): 1) Ubuntu Mate 21.10 liveUSB with LO daily: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 1ffd6897ddf15624e70585ab08e8af713114c938 CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded 2) Win10 with LO portable: Edition Windows 10 Home Version 21H1 Installiert am 22.12.2020 Betriebssystembuild 19043.1586 Leistung Windows Feature Experience Pack 120.2212.4170.0 Driver date: 19.02.2020 Driver version: 26.20.100.7925 Version: 7.3.1.3 (x86) / LibreOffice Community Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded