Bug 669983 - [abrt] mysql-workbench-5.2.30-1.fc13: glibmm_unexpected_exception: Process /usr/bin/mysql-workbench-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] mysql-workbench-5.2.30-1.fc13: glibmm_unexpected_exception: Process /u...
Keywords:
Status: CLOSED DUPLICATE of bug 683047
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql-workbench
Version: 13
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:25bd085d68af6d2abcf72358b0e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-16 13:52 UTC by Asaf Mesika
Modified: 2011-03-09 16:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-09 16:12:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (84.49 KB, text/plain)
2011-01-16 13:52 UTC, Asaf Mesika
no flags Details

Description Asaf Mesika 2011-01-16 13:52:51 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-66.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: 1295184814
uid: 502

How to reproduce
-----
1. In SQL Editor, I right-clicked a table and chosed Edit. The table didn't appear as tab, but rather the last table edited remained there.
2. Did step 1, two more times and than while trying to edit a value in the table, (which was not the table I wanted) it crashed
3.

Comment 1 Asaf Mesika 2011-01-16 13:52:54 UTC
Created attachment 473703 [details]
File: backtrace

Comment 2 Remi Collet 2011-03-09 16:12:44 UTC

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


Note You need to log in before you can comment on or make changes to this bug.