Bug 674928 - [abrt] inkscape-0.48.0-1.fc14.3: Process /usr/bin/inkscape was killed by signal 11 (SIGSEGV)
Summary: [abrt] inkscape-0.48.0-1.fc14.3: Process /usr/bin/inkscape was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 659927
Alias: None
Product: Fedora
Classification: Fedora
Component: inkscape
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:403ef0d2e55069c53dd378dc2ff...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-03 18:46 UTC by Mads Kiilerich
Modified: 2012-03-20 18:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-20 18:35:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (29.29 KB, text/plain)
2011-02-03 18:46 UTC, Mads Kiilerich
no flags Details

Description Mads Kiilerich 2011-02-03 18:46:01 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: inkscape
component: inkscape
executable: /usr/bin/inkscape
kernel: 2.6.35.10-74.fc14.i686.PAE
package: inkscape-0.48.0-1.fc14.3
reason: Process /usr/bin/inkscape was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296758018
uid: 500

How to reproduce
-----
Inkscape newbie here, creating some texts, and drawing some arrows.
I cloned the arrows with ctrl+d, moved them with the select tool and adjusted with node tool. I noticed that sometimes the node manipulation of the clone source sometimes was lost when I started manipulating the clone. Shortly after it crashes

2.
3.

Comment 1 Mads Kiilerich 2011-02-03 18:46:04 UTC
Created attachment 476844 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-20 18:35:31 UTC
Backtrace analysis found this bug to be similar to bug #659927, closing as duplicate.

Bugs which were found to be similar to this bug: bug #659927, bug #663534

This comment is automatically generated.

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


Note You need to log in before you can comment on or make changes to this bug.