Bug 700931

Summary: [abrt] synfigstudio-0.62.00-2.fc13: Process /usr/bin/synfigstudio was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: blue_t_fox
Component: synfigstudioAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: lkundrak, luya_tfz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:68b4255f6435a39339ea45511e6831db11b211f0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:29:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description blue_t_fox 2011-04-29 19:59:30 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 28377 bytes
cmdline: /usr/bin/synfigstudio
comment: Installed synfig and started it up, after a second or two the program crashed on its own without any interaction.
component: synfigstudio
Attached file: coredump, 34828288 bytes
crash_function: studio::WorkArea::on_drawing_area_event
executable: /usr/bin/synfigstudio
kernel: 2.6.35.12-90.fc14.x86_64
package: synfigstudio-0.62.00-2.fc13
rating: 4
reason: Process /usr/bin/synfigstudio was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: Simply started up the program after installation.
time: 1304106287
uid: 500
Comment 1 blue_t_fox 2011-04-29 19:59:33 UTC 
Created attachment 495862 [details]
File: backtrace
Comment 2 blue_t_fox 2011-04-30 17:55:08 UTC 
This doesn't happen with the RPM provided on the Synfig Studio homepage incidentally, though I don't know what the differences are between the two. But the version in F14's repositories crashes immediately upon opening.
Comment 3 abrt-bot 2012-03-21 14:29:48 UTC 
Backtrace analysis found this bug to be similar to bug #657387, closing as duplicate.

Bugs which were found to be similar to this bug: bug #640863, bug #657387

This comment is automatically generated.

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