Bug 673553

Summary: [abrt] mysql-workbench-5.2.30-1.fc14: Process /usr/bin/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jan Sipikal <jan.sipikal>
Component: mysql-workbenchAssignee: Remi Collet <fedora>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: fedora, xrouby
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:c75d2c64a043aedef1199a42a5b620437ca6990b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-09 16:11:00 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 Jan Sipikal 2011-01-28 17:22:35 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/mysql-workbench-bin
component: mysql-workbench
crash_function: sigc::internal::trackable_callback_list::remove_callback
executable: /usr/bin/mysql-workbench-bin
kernel: 2.6.35.10-74.fc14.i686
package: mysql-workbench-5.2.30-1.fc14
rating: 4
reason: Process /usr/bin/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296234858
uid: 500

How to reproduce
-----
1. open mysql workbench
2. import database
3. create err model and than program crash
Comment 1 Jan Sipikal 2011-01-28 17:22:37 UTC 
Created attachment 475836 [details]
File: backtrace
Comment 2 xrouby 2011-02-21 16:59:31 UTC 
Package: mysql-workbench-5.2.30-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. sudo yum install mysql-workbench.i686
2. start workbench GUI from the 'Application' menu
3. try several buttons
4. it crashes
Comment 3 Remi Collet 2011-03-09 16:11:00 UTC 

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