I am running LO 220.127.116.11 on Linux3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64 GNU/Linux.
I generated a chart in LO Calc that I wanted to export to SVG for further editing with Inkscape. From Calc, I copy-pasted the chart to an empty Draw picture and exported it as SVG. The SVG file I obtained appears to be invalid and did not open in Inkscape.
No detailed error message was produced by Inkscape, but Firefox and EOG both complained about the invalid file and gave some details:
EOG: "Error domain 1 code 76 on line 131 column 213 of file:///home/floflooo/Work/Copyrighter/db_copy_number/rrNDB/graph/bug/graph_test.svg: Opening and ending tag mismatch: tspan line 0 and text"
Firefox: "XML Parsing Error: mismatched tag. Expected: </tspan>.
Line Number 131, Column 373"
Upon further inspection of the XML, there seem to be two errors:
* missing </tspan> tag at the end of line 130
* extra slash in tag <text class="TextShape"/> at line 131
I have attached the ODG file that generates the invalid SVG file, the invalid SVG file itself, and my corrected version of the SVG file.
Created attachment 83271 [details]
ODG file that generates the invalid SVG file
Created attachment 83272 [details]
Invalid SVG file
Created attachment 83273 [details]
Manually corrected SVG file
Reproducible under Fedora 19 (64-bit) with 18.104.22.168, and also with 22.214.171.124.alpha0+
Build ID: f4004429d339009bec6babe30becdc9c727940b8
TinderBox: Linux-x86-64@8-SLED11, Branch:master, Time: 2013-08-18_23:20:11
Bug 65788 added to See Also list. Both issues deal with a Calc chart pasted into Draw and then exported to SVG with the resultant SVG being treated differently (or not at all in this case) by Inkscape.
Problem still reproducible (neither Draw nor Inkscape v0.48.3.1 r9886 can open the exported SVG) under GNU/Linux using:
- v126.96.36.199 Build ID: 08ebe52789a201dd7d38ef653ef7a48925e7f9f7
- v188.8.131.52.alpha0+ Build ID: 4aa9b041de3129f19b48e66d349f48657b73f33e (2014-07-19)
** 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 on a currently supported version of LibreOffice (184.108.40.206 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
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)
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: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
LibreOffice 220.127.116.11: still affected by the bug
LibreOffice 18.104.22.168: all seems to work alright
This is on Linux x86-64
Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":
crashtesting: assert on conversion of fdo67521-1.odg to pdf
It will be available in 7.3.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:
Affected users are encouraged to test the fix and report feedback.