Bug 683695 - [abrt] xchat-1:2.8.8-6.fc14: _gdk_x11_window_tmp_unset_bg: Process /usr/bin/xchat was killed by signal 7 (SIGBUS)
[abrt] xchat-1:2.8.8-6.fc14: _gdk_x11_window_tmp_unset_bg: Process /usr/bin/x...
Product: Fedora
Classification: Fedora
Component: xchat (Show other bugs)
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jonathan Blandford
Fedora Extras Quality Assurance
: 663558 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2011-03-09 22:37 EST by Dimi Paun
Modified: 2013-04-02 00:25 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-16 09:38:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (24.97 KB, text/plain)
2011-03-09 22:37 EST, Dimi Paun
no flags Details

  None (edit)
Description Dimi Paun 2011-03-09 22:37:04 EST
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 25573 bytes
cmdline: xchat
component: xchat
Attached file: coredump, 12517376 bytes
crash_function: _gdk_x11_window_tmp_unset_bg
executable: /usr/bin/xchat
package: xchat-1:2.8.8-6.fc14
rating: 4
reason: Process /usr/bin/xchat was killed by signal 7 (SIGBUS)
release: Fedora release 14 (Laughlin)
time: 1299608506
uid: 500

How to reproduce
1. Just crashed.
Comment 1 Dimi Paun 2011-03-09 22:37:07 EST
Created attachment 483348 [details]
File: backtrace
Comment 3 abrt-bot 2012-03-20 14:10:26 EDT
Backtrace analysis of bugs across components suggests the actual bug might be in component glibc instead of component xchat. You might want to inspect the backtrace from the bug listed below to find out the correct component.

Bug #663558 from component notification-daemon was found to be similar to this bug.

This comment is automatically generated.
Comment 4 abrt-bot 2012-03-20 14:10:34 EDT
*** Bug 663558 has been marked as a duplicate of this bug. ***
Comment 5 Fedora End Of Life 2012-08-16 09:38:45 EDT
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

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