Bug 105398 - FILEOPEN PPTX Arrow aligned wrong
Summary: FILEOPEN PPTX Arrow aligned wrong
Status: RESOLVED DUPLICATE of bug 89449
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pptx
Depends on:
Blocks: PPTX
  Show dependency treegraph
 
Reported: 2017-01-17 22:02 UTC by Haleh Alemasoom
Modified: 2021-01-14 10:17 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
photo of misplaced arrows vs original + original slide (31.02 KB, application/zip)
2017-01-17 22:02 UTC, Haleh Alemasoom
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Haleh Alemasoom 2017-01-17 22:02:13 UTC
Created attachment 130507 [details]
photo of misplaced arrows vs original + original slide

1. Opened a microsoft pptx file containing a flowchart in LibreOffice Impress
2. The arrows in the flowchart are misplaced
Comment 1 Buovjaga 2017-01-24 07:40:20 UTC
Confirmed. In 3.5 the arrow is not even shown. In 4.1 the arrow does a huge trip from the *right side*. I'll set the earliest to be 4.3 as it shows the same error as current.

Win 7 Pro 64-bit Version: 5.4.0.0.alpha0+
Build ID: 1c27286b9d5331634c073cd3e327bd941e61bbb6
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2017-01-23_03:24:17
Locale: fi-FI (fi_FI); Calc: group
Comment 2 QA Administrators 2019-03-17 03:51:57 UTC Comment hidden (obsolete)
Comment 3 Buovjaga 2019-09-29 12:18:21 UTC
Still confirmed

Version: 6.4.0.0.alpha0+ (x64)
Build ID: e1b51d4588b4b39592bb94dd5bb90de5e04d061e
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-23_09:16:11
Locale: fi-FI (fi_FI); UI-Language: en-US
Calc: threaded
Comment 4 NISZ LibreOffice Team 2021-01-14 10:17:48 UTC
This is a simple connector shape, which is incorrectly imported.

*** This bug has been marked as a duplicate of bug 89449 ***