This is pulled from bug 81818 steps: 1. open attachment 97256 [details] 2. goto slide 6 or 19 3. notice formulas have an OLE icon in them screenshot - attachment 103560 [details] This icon only appears on windows, so the question is whether this icon should be there and why is it only appearing on windows and not linux. Version: 6.0.0.0.alpha0+ Build ID: 4d1ee296def5fde9c77702d3d19d76be33cbdaad CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: en-US (en_US); Calc: group
So the OLE icon used to also appear in linux, as can be seen in 4.0.6, but its gone in 4.2.8.
The commit that fixes bug 81818 on Linux is the following (bibisected using bibisect-44max): https://cgit.freedesktop.org/libreoffice/core/commit/?id=0aa3dee5e88a1494a7a6a8401e084cbdb4324727 author Armin Le Grand <alg@apache.org> 2014-07-09 11:57:21 (GMT) committer Caolán McNamara <caolanm@redhat.com> 2014-07-09 12:59:10 (GMT) Resolves: #i119287# corrected default style for draw objects...
** 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 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still repro in Version: 6.2.0.0.alpha0+ Build ID: d9ad59da50c1172fe98f94370221c9c1b688200a CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-10-08_23:34:44 Locale: ru-RU (ru_RU); Calc: threaded
Still confirmed. In 3.3.0 it shows text "Object 5". Version: 6.4.0.0.alpha0+ (x64) Build ID: d744838991594eebe27acc4c7d9fb4579d654853 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-09-29_05:12:00 Locale: fi-FI (fi_FI); UI-Language: en-US Calc: threaded
Another example in LO 6.5+ is PPTX attachment 144411 [details] from bug 101100.
I see this as solved (attachment 97256 [details] and attachment 144411 [details] both look good) in 7.3 since: https://git.libreoffice.org/core/+/92a407b7f90a98704a238c5ffa3a3491eaf3263a author Gülşah Köse <gulsah.kose@collabora.com> Wed Jul 07 00:27:58 2021 +0300 committer Gülşah Köse <gulsah.kose@collabora.com> Thu Jul 08 23:12:07 2021 +0200 tree 24eecc3bbf5e0547167787e71b4573d1af957116 parent 3175a7684982e7812e8071c595395eb3da3035fc [diff] tdf143222 Handle alternate content of graphicData element. Thanks Gülşah for fixing this! *** This bug has been marked as a duplicate of bug 143222 ***