Bug 105513 - Messed up chart after openning pptx in Impress
Summary: Messed up chart after openning pptx in Impress
Status: RESOLVED DUPLICATE of bug 102186
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
5.2.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2017-01-25 01:34 UTC by Haleh Alemasoom
Modified: 2018-03-16 23:50 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
bug image + original doc file (69.66 KB, application/zip)
2017-01-25 01:34 UTC, Haleh Alemasoom 		Details
document (36.37 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2017-01-25 10:42 UTC, Xisco Faulí 		Details
comparison (48.98 KB, image/png)
2017-01-25 10:42 UTC, Xisco Faulí 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Haleh Alemasoom 2017-01-25 01:34:57 UTC 
Created attachment 130667 [details]
bug image + original doc file

1. open attached pptx in LibreOffice 5.2
2. the chart is messy with extra lines added
Comment 1 Xisco Faulí 2017-01-25 10:42:40 UTC 
Created attachment 130670 [details]
document
Comment 2 Xisco Faulí 2017-01-25 10:42:56 UTC 
Created attachment 130671 [details]
comparison
Comment 3 Xisco Faulí 2017-01-25 10:50:27 UTC 
Confirmed in

Version: 5.4.0.0.alpha0+
Build ID: d3ff66999d924e832f8219c65ced0526f1a67f82
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Rendering problem introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=3df94a9272260cd839f6aec69d9f4914fc1ba565..5fa0adf25cfcb71129e05e7218cde46874306c15

Adding Cc: to Markus Mohrhard

Colour problem reported in bug 105517
Comment 4 Aron Budea 2017-08-28 00:20:18 UTC 
Looks like a duplicate of bug 102186.

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