Bug 668942 - [abrt] xchat-1:2.8.8-6.fc14: rb_bug: Process /usr/bin/xchat was killed by signal 6 (SIGABRT)
[abrt] xchat-1:2.8.8-6.fc14: rb_bug: Process /usr/bin/xchat was killed by sig...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: xchat (Show other bugs)
14
i686 Unspecified
low Severity medium
: ---
: ---
Assigned To: Christopher Aillon
Fedora Extras Quality Assurance
abrt_hash:fc660538d7bbb1aed734218caa1...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-12 01:30 EST by Randall "Randy" Berry
Modified: 2011-11-24 02:13 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-11-24 02:13:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (15.44 KB, text/plain)
2011-01-12 01:30 EST, Randall "Randy" Berry
no flags Details

  None (edit)
Description Randall "Randy" Berry 2011-01-12 01:30:42 EST
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: xchat
comment: This is the first time this has happened. I opened and clost the application several times since the crash and it exited gracefully.
component: xchat
crash_function: rb_bug
executable: /usr/bin/xchat
kernel: 2.6.35.10-74.fc14.i686.PAE
package: xchat-1:2.8.8-6.fc14
rating: 4
reason: Process /usr/bin/xchat was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1294812886
uid: 501

How to reproduce
-----
1. Closed out the application and it crashed.
2.
3.
Comment 1 Randall "Randy" Berry 2011-01-12 01:30:44 EST
Created attachment 472958 [details]
File: backtrace
Comment 2 Randall "Randy" Berry 2011-11-24 02:13:02 EST
This bug has been open for a while now and the incident has never reproduced itself. Closing it. F14 is also nearing end of life.

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