Bug 64550 - [SVG import] overlaying nodes drawn wrong
Summary: [SVG import] overlaying nodes drawn wrong
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
(earliest affected) rc
Hardware: Other All
: medium minor
Assignee: Not Assigned
Whiteboard: need
Depends on:
Reported: 2013-05-13 15:24 UTC by ilikebigbugs
Modified: 2015-02-11 19:47 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:

image of the behaviour (40.33 KB, image/png)
2013-05-13 15:24 UTC, ilikebigbugs
example svg (3.69 KB, image/svg+xml)
2013-05-13 15:26 UTC, ilikebigbugs
LO at 600percent zoom (50.90 KB, image/png)
2014-05-04 11:30 UTC, retired

Note You need to log in before you can comment on or make changes to this bug.
Description ilikebigbugs 2013-05-13 15:24:30 UTC
Created attachment 79255 [details]
image of the behaviour

the path is drawn wrong where two nodes overlay
Comment 1 ilikebigbugs 2013-05-13 15:26:42 UTC
Created attachment 79256 [details]
example svg

take care its a very tiny drawing at the left side (may look like there is nothing in the drawing)
Comment 2 Jorendc 2013-06-20 23:42:50 UTC
I can confirm this behavior using Mac OSX 10.8.3 with LibreOffice Version: Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155; 

Kind regards,
Comment 3 retired 2014-03-30 09:36:14 UTC
Steps to reproduce? Please attach a test LO document for easy reproduction and further testing of this problem.

After providing that, please set the bug back to "NEW".
Comment 4 retired 2014-05-04 11:29:48 UTC
Wow, I'm confused. I inserted the SVG in question. It's so tiny, that at 600% zoom in LO I almost see anything (screenshot attached).

I'm confused as to what of make of this, as to the practical implications of this "bug". Is it a bug at all?
Comment 5 retired 2014-05-04 11:30:26 UTC
Created attachment 98413 [details]
LO at 600percent zoom
Comment 6 retired 2014-05-04 11:30:58 UTC
@ilikebigbugs: Is this bug still valid / reproducible with the latest LO release?  Currently 4.2.3: http://www.libreoffice.org/download/libreoffice-fresh/

Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME.

Setting to NEEDINFO until more detail is provided.
Comment 7 QA Administrators 2015-01-10 18:06:14 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

Message generated on: 10/01/2015
Comment 8 QA Administrators 2015-02-11 19:47:53 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO

Message generated on: 2015-02-11