Display bug on a complex shape SVG made with inkscape

Bug #1379291 reported by Popolon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Medium
Unassigned

Bug Description

This is probably a bug linked to a specific shape case.

The SVG is quite simple, only two planes, with one shape on each, but shapes themselves are rather complexes.

The SVG made with inkscape, exported as simple SVG, display well in Firefox and WebKit browsers. Gimp can import it without problems.

Inkscape, at display, at bitmap export and inkview can't manage it.

Procedure to make this picture (goal was to have similar feeling than linocut/woodcut) :
* The shape with made with 2 layers 1 for black background, another with fountainpen like drawing, with lot of lines.
* The lines are transformed to one shape using union boolean
* The resulting shape is cuted in the black shape using difference boolean
* The new black shape is slightly simplified using simplify (ctrl+l) with 0.0005 simplification threeshold.

Tags: renderer
Revision history for this message
Popolon (popolon) wrote :
Revision history for this message
Popolon (popolon) wrote :

Clicking on SVGZ make an erroenous bug on launchpad, because server miss SVGZ configuration (need content-encoding: gzip for SVGZ).

The same exact file works when the web-server has good configuration :

http://popolon.org/Moulin_fouleur.web.svgz

Revision history for this message
Popolon (popolon) wrote :

Another detail inforamtion, when I drawed the lines in a different layer, everything displayed well, display bug started after some dimplification/and/or union/difference, I first think more about a refreshing bug as, the whole picture started to slowdown displaying control dots. I still have the original file, before applying booleans if this can help to debug.

Revision history for this message
jazzynico (jazzynico) wrote :

Reproduced on Windows XP, Inkscape 0.48.5 (lower part of the drawing is missing).
Not reproduced with revision 13540.

Could you please confirm it's the same bug (see attached screenshot) and that it only affects the the 0.48 branch?
Thanks!

tags: added: renderer
Revision history for this message
Popolon (popolon) wrote :

Yes. same bug, I use Inkscape 0.48.5r (ubuntu package 0.48.5+32~ubuntu14.04.1)

Revision history for this message
Popolon (popolon) wrote :

Confirm that works fine in inkscape 0.91pre2 (revision 13586) I just installed :)

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

Based on tests with archived builds (on OS X 10.7.5), the rendering issue was fixed with the merge of the cairo-renderer branch in r10326:
- reproduced with 0.47, 0.48.5
- reproduced with trunk rev <= 10325
- not reproduced with trunk rev >= 10326

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

Similar earlier report about complex paths not fully rendered:
- Bug #428415 “Portions of path not drawn on screen or exported”
  <https://bugs.launchpad.net/inkscape/+bug/428415>
- Bug #235825 “Exporting filled Pattern Along Path loses random fill color”
  <https://bugs.launchpad.net/inkscape/+bug/235825>

AFAICT in the reporter's example file here (bug #1379291), only the 'fill' of the complex path is affected: the stroke of the same path renders correctly (in stable 0.48.5).

Revision history for this message
Popolon (popolon) wrote :

Tbe 3 shapes user here don't use stroke, but only fill, so that's looks really like the same bug. A really complexe shape, with probably a memory limit reached or something like that.

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

Does not reproduce with new renderer in Inkscape >= 0.91.

Changed in inkscape:
importance: Undecided → Medium
milestone: none → 0.91
status: New → Fix Released
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.