Bug 664755

Summary: [abrt] mysql-workbench-5.2.30-1.fc13: glibmm_unexpected_exception: Process /usr/bin/mysql-workbench-bin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Adam Carbone <acarbs12>
Component: mysql-workbenchAssignee: Remi Collet <fedora>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:434102da675623f7f5e5e18e033a5bd9d019e265
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-09 16:13:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Adam Carbone 2010-12-21 15:11:20 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/mysql-workbench-bin
component: mysql-workbench
crash_function: glibmm_unexpected_exception
executable: /usr/bin/mysql-workbench-bin
kernel: 2.6.34.7-61.fc13.x86_64
package: mysql-workbench-5.2.30-1.fc13
rating: 4
reason: Process /usr/bin/mysql-workbench-bin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1292943964
uid: 500

How to reproduce
-----
1.trying to reconnect to the DB
2.
3.
Comment 1 Adam Carbone 2010-12-21 15:11:23 UTC 
Created attachment 469998 [details]
File: backtrace
Comment 2 Remi Collet 2011-03-09 16:13:50 UTC 
I hope new version (which fixes a lot of bug) will fixes this one.

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