Bug 701752 - [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:0f80cc96fa11a367184f82eebe5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-03 18:53 UTC by Juan Carlos Watts
Modified: 2011-06-10 14:22 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (33.76 KB, text/plain)
2011-05-03 18:53 UTC, Juan Carlos Watts 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Juan Carlos Watts 2011-05-03 18:53:57 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 34573 bytes
cmdline: /usr/bin/mysql-workbench-bin
component: mysql-workbench
Attached file: coredump, 117678080 bytes
crash_function: glibmm_unexpected_exception
executable: /usr/bin/mysql-workbench-bin
kernel: 2.6.35.12-88.fc14.i686.PAE
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: 1304448573
uid: 500

How to reproduce
-----
1.Only execute a select
2.
3.
Comment 1 Juan Carlos Watts 2011-05-03 18:53:58 UTC 
Created attachment 496614 [details]
File: backtrace
Comment 2 Juan Carlos Watts 2011-05-27 21:41:26 UTC 
Package: mysql-workbench-5.2.33b-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Only execute a select
2.
3.
Comment 3 Remi Collet 2011-06-10 14:22:04 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.