Bug 695111

Summary: [abrt] bluefish-2.0.3-3.fc14: g_main_context_check: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: George Tat <geotri314>
Component: bluefishAssignee: Paul Howarth <paul>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: paul
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:b28cd5316d084fb9527693dad43839a5545f0f2a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 14:12:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description George Tat 2011-04-10 16:27:37 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 25427 bytes
cmdline: bluefish
component: bluefish
Attached file: coredump, 48558080 bytes
crash_function: g_main_context_check
executable: /usr/bin/bluefish
kernel: 2.6.35.11-83.fc14.i686.PAE
package: bluefish-2.0.3-3.fc14
rating: 4
reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302259370
uid: 500

How to reproduce
-----
1.i killed the app from konsole using kill command
2.
3.
Comment 1 George Tat 2011-04-10 16:27:41 UTC 
Created attachment 491090 [details]
File: backtrace
Comment 2 Paul Howarth 2011-04-18 15:16:54 UTC 
Why did you kill the app?
Comment 3 abrt-bot 2012-03-30 14:12:00 UTC 
Backtrace analysis found this bug to be similar to bug #699927, closing as duplicate. This bug seems to belong to component gtk2.

Bugs which were found to be similar to this bug: 
  evolution: bug #661543
  gnome-media: bug #564193
  gnome-packagekit: bug #615760
  gnome-settings-daemon: bug #699927
  libucil: bug #669993
  synce-trayicon: bug #564199

This comment is automatically generated.

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