Crash when moving node in a polygon with a pattern fill

Bug #573139 reported by pottersson
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

The following steps get Inkscape 0.47~pre4-0ubuntu (the latest version from the repos on Ubuntu 9.10 Karmic Koala) to crash 100% of the time:

1) Open Inkscape
2) Use the Polygon tool to create a shape (I was making quadrilaterals)
3) Use the Ctrl+Shift+F pane to change the fill to the default pattern
4) Use the Node Tool
5) Select a single node on the polygon and move it.

The program should crash.

Here's the gdb backtrace:

user@host:/usr/bin$ gdb /usr/bin/inkscape
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/inkscape...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/inkscape
[Thread debugging using libthread_db enabled]

** (inkscape:8134): CRITICAL **: virtual const gchar* Inkscape::XML::SimpleNode::attribute(const gchar*) const: assertion `name != NULL' failed

** (inkscape:8134): CRITICAL **: virtual void Inkscape::XML::SimpleNode::setAttribute(const gchar*, const gchar*, bool): assertion `name && *name' failed

Program received signal SIGSEGV, Segmentation fault.
0x080927c5 in ?? ()
(gdb)

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

linking as duplicate to bug #463602 “crash when node-editing pattern-filled object”
<https://bugs.launchpad.net/inkscape/+bug/463602>

Please add a comment and revert the duplicate status if you don't agree and think these are different issues.

tags: added: crash node-editing pattern
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.