lindenmayer.py crashed with IOError in lxml.etree._FilelikeWriter.write (src/lxml/lxml.etree.c:92532)(): [Errno 32] Broken pipe

Bug #946599 reported by Thomas Chamberlain
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Medium
Unassigned
inkscape (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This happened as I was rendering with L-System

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: inkscape 0.48.3.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sun Mar 4 20:05:07 2012
ExecutablePath: /usr/share/inkscape/extensions/lindenmayer.py
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python lindenmayer.py --id=path2990 --tab="rules" --axiom=F --rules=F=F[+F]F[-F]F[+F[+F]F]F[+F]F[-F]F[-F[+F]F[-F[+F]F]F[+F]F[-F]F]F[+F]F[-F]F[+F[+F]F]F[-F]F[-F[+F]F]F[-F]F[-F[+F]F[+F[+F]F[-F]F]F[-F]F[-F[+F]F]F[+F]F[+F[+F]F[-F[-F]F]F[-F]F]F[+F]F[+F[-F]F]F[-F]F[-F[+F]F[-F]F[+F[+F]F]F[-F]F]F[+F]F[-F]F[+F[+F]F]F[+F]F[-F[+F]F]F[-F]F]F[-F]F[+F[-F]F]F[-F]F[+F[+F]F[-F[-F]F]F[+F]F[-F]F]F[-F]F[+F[+F]F[-F]F]F[+F]F[-F]F[-F[+F]F[-F]F[+F[+F]F[-F]F]F[+F]F[-F]F[-F[+F]F]F[-F]F]F[-F]F[-F[+F]F]F --order=2 --step=25 --randomizestep=0 --langle=16 --rangle=16 --randomizeangle=0 /tmp/ink_ext_XXXXXX.svg3I5TAW
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PythonArgs: ['lindenmayer.py', '--id=path2990', '--tab="rules"', '--axiom=F', '--rules=F=F[+F]F[-F]F[+F[+F]F]F[+F]F[-F]F[-F[+F]F[-F[+F]F]F[+F]F[-F]F]F[+F]F[-F]F[+F[+F]F]F[-F]F[-F[+F]F]F[-F]F[-F[+F]F[+F[+F]F[-F]F]F[-F]F[-F[+F]F]F[+F]F[+F[+F]F[-F[-F]F]F[-F]F]F[+F]F[+F[-F]F]F[-F]F[-F[+F]F[-F]F[+F[+F]F]F[-F]F]F[+F]F[-F]F[+F[+F]F]F[+F]F[-F[+F]F]F[-F]F]F[-F]F[+F[-F]F]F[-F]F[+F[+F]F[-F[-F]F]F[+F]F[-F]F]F[-F]F[+F[+F]F[-F]F]F[+F]F[-F]F[-F[+F]F[-F]F[+F[+F]F[-F]F]F[+F]F[-F]F[-F[+F]F]F[-F]F]F[-F]F[-F[+F]F]F', '--order=2', '--step=25', '--randomizestep=0', '--langle=16', '--rangle=16', '--randomizeangle=0', '/tmp/ink_ext_XXXXXX.svg3I5TAW']
SourcePackage: inkscape
Title: lindenmayer.py crashed with IOError in lxml.etree._FilelikeWriter.write (src/lxml/lxml.etree.c:92532)(): [Errno 32] Broken pipe
UpgradeStatus: Upgraded to precise on 2012-02-27 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Thomas Chamberlain (thomazchamberlain) wrote :
tags: removed: need-duplicate-check
visibility: private → public
tags: added: crash extensions-plugins
Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Windows XP, Inkscape 0.48.3.1 and trunk revision 11129.
Generated file attached

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

Not reproduced on OS X 10.7.2 with Inkscape 0.48.3.1 and current trunk r11129, Python 2.7.2

Changed in inkscape (Ubuntu):
importance: Undecided → Medium
Changed in inkscape:
importance: Undecided → High
Revision history for this message
su_v (suv-lp) wrote :

> Changed in inkscape:
> importance: Undecided → High

Should be lowered to 'Medium' IMHO: it's "only" the separately spawned python process which "crashes" (on Ubuntu 12.04) - i.e. executing the extension fails. The main Inkscape process itself is not affected, and there is no risk of data loss involved due to unsaved changes in the SVG file.

jazzynico (jazzynico)
Changed in inkscape:
importance: High → Medium
Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Debian testing, Inkscape 0.48.3.1 and trunk revision 11992.

Revision history for this message
Kris (kris-degussem) wrote :

Not reproduced on Inkscape 0.48.x r9945 (vista 64 bit)
Closing report because the issue could not be reproduced on various systems.

Changed in inkscape:
status: New → Invalid
Mattia Rizzolo (mapreri)
Changed in inkscape (Ubuntu):
status: New → Invalid
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.