Bug 713715

Summary: [abrt] xchat-gnome-0.26.1-14.fc14: channel_is_autojoin: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: arhi.smece
Component: xchat-gnomeAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: notting, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:102d8175961bfad62afd70d1ee82ec2f96c8e8be
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-16 19:17:57 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 arhi.smece 2011-06-16 11:11:22 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 26868 bytes
cmdline: xchat-gnome
comment: start - crash
component: xchat-gnome
Attached file: coredump, 73351168 bytes
crash_function: channel_is_autojoin
executable: /usr/bin/xchat-gnome
kernel: 2.6.35.13-92.fc14.x86_64
package: xchat-gnome-0.26.1-14.fc14
rating: 4
reason: Process /usr/bin/xchat-gnome was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: start - crash
time: 1308222470
uid: 500
Comment 1 arhi.smece 2011-06-16 11:11:25 UTC 
Created attachment 505018 [details]
File: backtrace
Comment 2 arhi.smece 2011-06-16 11:12:45 UTC 
Package: xchat-gnome-0.26.1-14.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
start - crash

Comment
-----
start - crash
Comment 3 arhi.smece 2011-06-16 11:24:28 UTC 
Package: xchat-gnome-0.26.1-14.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
start - crash

Comment
-----
start - crash
Comment 4 Bill Nottingham 2011-06-16 19:17:57 UTC 

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