Bug 83275 - FILEOPEN: VDX import just throws general I/O error
Summary: FILEOPEN: VDX import just throws general I/O error
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
4.1.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: target:4.3.0
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-30 14:14 UTC by Hans Breuer
Modified: 2015-04-08 10:20 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
render-test.vdx generated by Dia master giving generic I/O error (595.33 KB, application/vnd.visio.xml)
2014-08-30 14:14 UTC, Hans Breuer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hans Breuer 2014-08-30 14:14:51 UTC
Created attachment 105469 [details]
render-test.vdx generated by Dia master giving generic I/O error

Loading render-test.vdx gnerated by Dia into Draw gives general I/O error when inline images are part of the file. This is caused by additional whitespace after the base64 encoded data of <ForeignData>.
Microsoft Visio Viewer 2010 handles the same file just fine.

I'll probably add a work-around to Dia to avoid this specific problem.
Comment 1 Hans Breuer 2014-08-30 15:18:31 UTC
Might be specific to version 4.2.4.2 or Linux. I've just checked the VDX with 4.3.0.4 portable under Windows and it's imported without the error.
Comment 2 Julien Nabet 2014-08-31 14:00:12 UTC
On pc Debian x86-64 with 4.3.0.4 Debian package, I could open it.

Which Linux distrib do you use?
Comment 3 MM 2014-08-31 14:23:18 UTC
Confirmed with V4.2.6.3 under windows 7 x64
Confirmed with V4.2.6.2 under mint 16 x64
Unconfirmed with V4.3.1.2 under mint 16 x64

Seems this bug has already been fixed in the 4.3 branch, but not backported to the 4.2 branch.

Set to NEW.
Comment 4 Julien Nabet 2014-08-31 14:37:37 UTC
Fridrich: I noticed that libvisio is different between 4.3 and 4.2 sources
(libvisio-0.0.31.tar.bz2 libvisio-0.1.0.tar.bz2)
Do you think it could be relevant to backport in 4.2 or should be put this one to FIXED (+ adding target 4.3.0.4)?
Comment 5 David Tardon 2014-09-01 08:09:45 UTC
(In reply to comment #4)
> Fridrich: I noticed that libvisio is different between 4.3 and 4.2 sources
> (libvisio-0.0.31.tar.bz2 libvisio-0.1.0.tar.bz2)
> Do you think it could be relevant to backport in 4.2 or should be put this
> one to FIXED (+ adding target 4.3.0.4)?

It is not possible to backport libvisio-0.1.0 to 4.2--it would have to be a backport of the single commit that fixed the problem (I assume that would not be hard, but I might be mistaken.) Anyway, 4.2 is just before the last bugfix release and this is not a regression in 4.2, so I am inclined not to do anything.