Steps to reproduce: 1. Open attached document Observed behaviour:
Steps to reproduce: 1. Open attached document Observed behaviour: Arrows connecting the blocks aren't imported. Reproduced in Version: 6.0.0.0.alpha0+ Build ID: 616f21db9e50a77b0c02dfb123f871a742f46216 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group and in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Created attachment 137052 [details] Block cycle's arrows not imported
Created attachment 137053 [details] comparison MSO 2010 and LibreOffice 6.0
Created attachment 137054 [details] Not reproduced when using 'Text Cycle'
Confirmed. Version: 6.0.0.0.alpha0+ Build ID: 616f21db9e50a77b0c02dfb123f871a742f46216 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3;
** 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 confirmed 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
still a bug in LO 6.4.1
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b9867f8b884ae8870a71b61e36f23eda91987e2a crashtesting: mismatched start/end tag assert on reexport of tdf113187-1.pptx It will be available in 7.0.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Dear Xisco Faulí, 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
Still reproducible in Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 9f0e19721bb598c75835cfa94f4158085f81288e CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-US (es_ES.UTF-8); UI: en-US Calc: threaded
This is not a normal SmartArt as available in the UI of PowerPoint. But the arrows are defined by a custGeom. In a normal SmartArt shapes only shapes with prstGeom are used. The geometry has a viewBox="0 0 0 0" but the subView is missing. The conversion from EMU to Hmm is missing. The rectangle of the arrows is on the correct place, but the path of the arrows is rendered at totally wrong place.
Created attachment 183345 [details] Shapes with arcto without any reference in path The SmartArt types "Block Cycle" and "Nondirectional Cycle" use arcTo commands. Each arcTo command introduces two additional equations for to convert start and swing angle from the unit 1/60000 degree in OOXML to degree in LibreOffice. Therefore maGuideList has items although all other points in the path have no references but constant values in if(!maGuideList.empty()) in https://opengrok.libreoffice.org/xref/core/oox/source/drawingml/customshapeproperties.cxx?r=c70ee4a6#201 That is the reason, why viewBox contains 0 for width and height and therefor the arc is not displayed. The error does not only exists with these SmartArt types, but with normal custom shapes with such geometry too, see attachment.
Regina Henschel committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/cf972fb9856957f4444199eb97464b83d8dc2698 tdf#113187 exclude angle conversion from count of maGuideList It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
*** Bug 125839 has been marked as a duplicate of this bug. ***
Regina Henschel committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/f0a86f50516c1f887b054fe0d042bf9be8c83975 tdf#113187 exclude angle conversion from count of maGuideList It will be available in 7.4.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
*** Bug 147975 has been marked as a duplicate of this bug. ***