Bug 706515 - [abrt] mysql-workbench-5.2.33b-1.fc14: glibmm_unexpected_exception: Process /usr/bin/mysql-workbench-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] mysql-workbench-5.2.33b-1.fc14: glibmm_unexpected_exception: Process /...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql-workbench
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:aa45e64551e382fa2f8c91a309e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-20 19:26 UTC by Andre Cruz
Modified: 2011-06-10 14:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-10 14:25:30 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (30.92 KB, text/plain)
2011-05-20 19:26 UTC, Andre Cruz 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Andre Cruz 2011-05-20 19:26:45 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 31665 bytes
cmdline: /usr/bin/mysql-workbench-bin
component: mysql-workbench
Attached file: coredump, 106696704 bytes
crash_function: glibmm_unexpected_exception
executable: /usr/bin/mysql-workbench-bin
kernel: 2.6.35.13-91.fc14.i686
package: mysql-workbench-5.2.33b-1.fc14
rating: 4
reason: Process /usr/bin/mysql-workbench-bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1305919381
uid: 500

How to reproduce
-----
1. Open 2 instances of Workbench (exec 2 times the app)
2. Close 1 instance
3. Try to use the second
Comment 1 Andre Cruz 2011-05-20 19:26:48 UTC 
Created attachment 500126 [details]
File: backtrace
Comment 2 krishanu007 2011-05-20 20:07:09 UTC 
Package: mysql-workbench-5.2.33b-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.WORKING WITH MYSQL WORKBENCH
2.
3.
Comment 3 Remi Collet 2011-06-10 14:25:30 UTC 
Version 5.2.34 is now available in the update.
Note You need to log in before you can comment on or make changes to this bug.