Bug 115455 - FILESAVE: DRAW Crashes when saving vsd file as odg
Summary: FILESAVE: DRAW Crashes when saving vsd file as odg
Status: RESOLVED DUPLICATE of bug 115429
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
5.4.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-05 07:59 UTC by Koen Roggemans
Modified: 2018-02-14 08:52 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
.vsd-file that crashes LODraw on saving as .odg (422.50 KB, application/vnd.visio)
2018-02-05 07:59 UTC, Koen Roggemans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Koen Roggemans 2018-02-05 07:59:23 UTC
Created attachment 139588 [details]
.vsd-file that crashes LODraw on saving as .odg

When opening (some) vsd file and saving it as odg using LibreOffice Draw, the application crashes and nothing is saved.

The vsd-file opens perfectly and is shown correctly on screen. The crash happens always, file edited or not. Tested on 2 different machines.

The file is in attachement for research purpose.
Comment 1 Julien Nabet 2018-02-05 08:26:41 UTC
On pc Debian x86-64 with LO Debian package 6.0.0.3, I don't reproduce this.
However, the odg can't open afterwards, like tdf#115429 put in See also.
Comment 2 Xisco Faulí 2018-02-05 11:43:37 UTC Comment hidden (obsolete)
Comment 3 Koen Roggemans 2018-02-05 13:03:35 UTC
I did a complete factory reset of the profile and the behaviour somewhat changed.
I can open the vsd-file, safe it as a odg. But when I try to open the odg, LibreOffice craches.
Comment 4 Julien Nabet 2018-02-05 13:14:20 UTC
(In reply to Koen Roggemans from comment #3)
> I did a complete factory reset of the profile and the behaviour somewhat
> changed.
> I can open the vsd-file, safe it as a odg. But when I try to open the odg,
> LibreOffice craches.

Just to be sure, before LO closes, do you see an error message?
Comment 5 Koen Roggemans 2018-02-05 13:19:43 UTC
Nu, unfortunately not.
Is there a way to turn some logging on?
Comment 6 Xisco Faulí 2018-02-05 13:50:29 UTC
(In reply to Koen Roggemans from comment #5)
> Nu, unfortunately not.
> Is there a way to turn some logging on?

You can download a debug version from http://dev-builds.libreoffice.org/daily/master/ ( the ones with -dbg at the end) and execute libreoffice with --backtrace as explained here https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux
Comment 7 Koen Roggemans 2018-02-14 08:25:41 UTC
Still present in LO Version: 6.0.1.1

Leesfout.
Fout in indeling opgemerkt in het bestand in subdocument content.xml op positie 2,3353(rij,kolom).

It's in the following part:
<style:graphic-properties ="evenodd" draw:stroke="none" draw:fill="solid" draw:fill-color="#b3b3b3" draw:shadow="hidden"/>

The error is about the space between graphic-properties and the = sign. That is column 3353. My XML-editor reports an error on column 3354, so there is something wrong there.
Comment 8 Koen Roggemans 2018-02-14 08:43:44 UTC
I found 2 occurrences of <style:graphic-properties ="evenodd"  in the content.xml part of the file. When I delete  ="evenodd" everywhere, the XML validates and the file works normally. (open, close, save, modify)

Comparing the vsd and the modified odg visually, I can't see anything missing by doing this.
Comment 9 Julien Nabet 2018-02-14 08:52:38 UTC
(In reply to Koen Roggemans from comment #8)
> I found 2 occurrences of <style:graphic-properties ="evenodd"  in the
> content.xml part of the file. When I delete  ="evenodd" everywhere, the XML
> validates and the file works normally. (open, close, save, modify)
> 
> Comparing the vsd and the modified odg visually, I can't see anything
> missing by doing this.

At beginning you said you had the crash when:
- opening vsd file
- save in odg

Then in your comment 3 you indicated you had the crash when:
- opening vsd file
- save in odg
- reopen the odg

So now it corresponds exactly to tdf#115429. I submitted a patch for review about this, see https://bugs.documentfoundation.org/show_bug.cgi?id=115429#c4

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