Created attachment 168698 [details] Simple PPTX slide Opening the attached document, there a strange red polygon appears in LibreOffice, that does not show in Office 365 (nor PowerPoint from what I've been told). Version: 7.2.0.0.alpha0+ Build ID: 1f1f68d6e8a32d8884e8de322e32c588a87964db CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-01-03_02:57:44 Calc: threaded Already in 6.4, too, so presumably not a (recent) regression: Version: 6.4.8.0.0+ Build ID: 99b065ec31d032fc08ab14f66430dac4fef904a5 CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-6-4, Time: 2020-10-08_08:57:08 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 168699 [details] Visual comparison Office 365 vs LibreOffice 7.2 (or 6.4)
file is PPT, but not PPTX I confirm in Version: 7.2.0.0.alpha0+ (x64) Build ID: 96bafa464ebdbce3ef04bec9beae5e745bb37794 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: CL and in Версия: 4.2.8.2 ID сборки: 48d50dbfc06349262c9d50868e5c1f630a573ebd
(In reply to Roman Kuznetsov from comment #2) > file is PPT, but not PPTX It actually is a PPTX, but with a .ppt extension.
Or just an incorrect MIME type, even.
Created attachment 173129 [details] MS PowerPoint, bottome left corner scaled up If you select this shape in LO, you will see that its BBox is a small square in the bottom left corner. If you now open this PPTX file in MS PowerPoint and try to select an area in the bottom left corner of the slide, you will select some "empty" square. Scale it up and you will see a very tiny version of the same shape. Navigator in LO lists it as "Autoshape 197". Most likely LO ignores/doesn't understand/fails to convert transformation matrix for that shape. Or maybe misunderstands units (meters instead of millimeters?). Someone skilled in MOOX could be able to say more.
Dear Gerald Pfeifer, 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 problem still exists in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d4ee93a54e790acab470667591d61d424831e665 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL threaded
LO generates a wrong viewBox. The problem is related to bug 76334, might be duplicate.