Bug 681330 - [abrt] mysql-workbench-5.2.30-1.fc14: gkr_operation_block_and_unref: Process /usr/bin/mysql-workbench-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] mysql-workbench-5.2.30-1.fc14: gkr_operation_block_and_unref: Process ...
Keywords:
Status: CLOSED DUPLICATE of bug 683047
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql-workbench
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7e11c1e9d55b144cdee67c9e53f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-01 18:59 UTC by Azeem Michael
Modified: 2011-03-09 16:13 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-09 16:13:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (31.93 KB, text/plain)
2011-03-01 18:59 UTC, Azeem Michael 		no flags Details
View All

Description Azeem Michael 2011-03-01 18:59:35 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 32692 bytes
cmdline: /usr/bin/mysql-workbench-bin
component: mysql-workbench
Attached file: coredump, 256483328 bytes
crash_function: gkr_operation_block_and_unref
executable: /usr/bin/mysql-workbench-bin
kernel: 2.6.35.11-83.fc14.x86_64
package: mysql-workbench-5.2.30-1.fc14
rating: 4
reason: Process /usr/bin/mysql-workbench-bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1299004617
uid: 500

How to reproduce
-----
1. I had two databases Edit windows open
2. stepped away from computer for a min
3. came back and all my sql query edit windows were gone. It was as if it had restarted on its own and there was a crash msg on panel.
Comment 1 Azeem Michael 2011-03-01 18:59:37 UTC 
Created attachment 481706 [details]
File: backtrace
Comment 2 Remi Collet 2011-03-09 16:13:03 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 ***
Note You need to log in before you can comment on or make changes to this bug.