svg corrupted after adding stroke to linked offset of text object

Bug #697126 reported by mds
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Inkscape
Confirmed
High
Unassigned

Bug Description

Inkscape 0.48
OS X 10.6.5 MacBook Pro [English]

Attached is the file that will load up ok, but after modifying will become corrupted (Inkscape/X presents me with a 'Inkscape encountered an internal error and will close now.' dialog). I can reliably reproduce this.

Steps:
Select outer most object (Linked Offset) on the text body 'poetry derived from bipolar poetry and crazyheadspace'
Add Stroke (fill) of R:0 G:118: B0 and size 1px.
Save file.

Expected:
To be able able to close off Inkscape and open the file back up.

Actual:
Presented with the error dialog quoted above when attempting to reopen. Inkscape doesn't crash when/after saving, ie I can continue editing, but the saved file becomes unusable.

Attached is a zip contain two svg's, logo.svg is the base graphic and logo-corrupted.svg is the graphic after saving with the above modification.

I couldn't see any logs in the app, the only info I could find was to make a custom build. I'll prob wait till this gets escalated/triaged before going down that path.

Tags: crash
Revision history for this message
mds (mark-sievers) wrote :
description: updated
Revision history for this message
su_v (suv-lp) wrote :

reproduced with Inkscape 0.48+devel r9994 on OS X 10.5.8
Inkscape opens 'logo.svg' (with some delay), and crashes when opening 'logo-corrupt.svg'.
Repeatable when saving 'logo.svg' after adding a stroke to the linked offset with the ID "path2994".

relevant diff between 'logo.svg' and 'logo-corrupt.svg':

106c106
< style="font-size:40px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#10c200;fill-opacity:1;stroke:none;font-family:Sans"
---
> style="font-size:40px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#10c200;fill-opacity:1;stroke:#007600;font-family:Sans;stroke-opacity:1;stroke-width:1.3;stroke-miterlimit:4;stroke-dasharray:none"

Backtrace attached.

I'm curious - did you at some point manually edit the SVG file (inserting a layer from a different document)?

Revision history for this message
su_v (suv-lp) wrote :

Duplicate of (or at least related to)
Bug #345371 “stroked and scaled Linked Offset text causes a crash upon open file”:
<https://bugs.launchpad.net/inkscape/+bug/345371>

Possibly bug #345371 is only triggered when the linked offset is stroked…

tags: added: crash
Changed in inkscape:
importance: Undecided → High
status: New → Confirmed
summary: - svg corrupted after adding stroke
+ svg corrupted after adding stroke to linked offset of text object
Revision history for this message
mds (mark-sievers) wrote :

Hi, cheers for the triage.

No manual modification at all, I only used the tools inside inkscape. I pretty much followed the tutorial here http://troy-sobotka.blogspot.com/2008/04/inkscape-tutorial-2-text-and-simple.html and just added a few more similar elements to get the graphic that you see.

Revision history for this message
mds (mark-sievers) wrote :

Just being fiddling about, and I think your theory around Linked Offset Strokes is close to the mark.

I have the same instance of logo-corrupted.svg open in inkscape that I used to produce it and removed the Stroke from the lower text boxes Linked Offset and the subsequently saved file opens okay. Still a little confusing as the upper text block has a Stroke applied to its linked offset yet has no problem.

Ive attached the original .svg of the the upper logo that I imported into logo.svg (via File > Import) which may or may not be useful to you.

Revision history for this message
su_v (suv-lp) wrote :

> I pretty much followed the tutorial here (…)
see <http://troy-sobotka.blogspot.com/2008/04/inkscape-tutorial-2-text-and-simple.html?showComment=1253617094252#c4154955661032700233> ;)

Linking as duplicate to bug #345371 to keep further discussion and tracking of the issue in one place. Please add a comment here and revert the duplicate status if you don't agree and think these are different issues which need to be tracked and fixed separately.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.