Bug 1262763

Summary: [abrt] hexchat: inbound_sasl_authenticate(): hexchat killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Andrew Cook <ariscop>
Component: hexchatAssignee: Patrick Griffis <tingping>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ariscop, praiskup, tingping
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/29b404b8d985a6a3dd3f9507d48a2c8dfe025107
Whiteboard: abrt_hash:1505b936a8686436d86276fdebcc3d4d7294f63a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-14 13:39:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Andrew Cook 2015-09-14 09:43:43 UTC 
Version-Release number of selected component:
hexchat-2.10.2-2.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        hexchat -e
crash_function: inbound_sasl_authenticate
executable:     /usr/bin/hexchat
global_pid:     22117
kernel:         4.1.6-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 inbound_sasl_authenticate at inbound.c:1871
 #1 process_named_servermsg at proto-irc.c:1347
 #2 irc_inline at proto-irc.c:1551
 #3 server_inline at server.c:404
 #4 server_read at server.c:469
 #9 gtk_main at gtkmain.c:1268
 #10 fe_main at fe-gtk.c:320
Comment 1 Andrew Cook 2015-09-14 09:43:48 UTC 
Created attachment 1073141 [details]
File: backtrace
Comment 2 Andrew Cook 2015-09-14 09:43:49 UTC 
Created attachment 1073142 [details]
File: cgroup
Comment 3 Andrew Cook 2015-09-14 09:43:51 UTC 
Created attachment 1073143 [details]
File: core_backtrace
Comment 4 Andrew Cook 2015-09-14 09:43:53 UTC 
Created attachment 1073144 [details]
File: dso_list
Comment 5 Andrew Cook 2015-09-14 09:43:55 UTC 
Created attachment 1073145 [details]
File: environ
Comment 6 Andrew Cook 2015-09-14 09:43:57 UTC 
Created attachment 1073146 [details]
File: limits
Comment 7 Andrew Cook 2015-09-14 09:44:01 UTC 
Created attachment 1073147 [details]
File: maps
Comment 8 Andrew Cook 2015-09-14 09:44:03 UTC 
Created attachment 1073148 [details]
File: mountinfo
Comment 9 Andrew Cook 2015-09-14 09:44:05 UTC 
Created attachment 1073149 [details]
File: namespaces
Comment 10 Andrew Cook 2015-09-14 09:44:06 UTC 
Created attachment 1073150 [details]
File: open_fds
Comment 11 Andrew Cook 2015-09-14 09:44:09 UTC 
Created attachment 1073151 [details]
File: proc_pid_status
Comment 12 Andrew Cook 2015-09-14 09:44:10 UTC 
Created attachment 1073152 [details]
File: var_log_messages
Comment 13 Patrick Griffis 2015-09-14 12:03:46 UTC 
Were you just using the SASL options in the network list?
Comment 14 Andrew Cook 2015-09-14 12:07:34 UTC 
I had just closed the network list (had to check something), SASL is set to EXTERNAL (ssl client cert), did not change any SASL settings though; Attempted to connect to a different server in the network (via /server command) and apparently crashed during sasl
Comment 15 Patrick Griffis 2015-09-14 13:01:14 UTC 
(In reply to Andrew Cook from comment #14)
> I had just closed the network list (had to check something), SASL is set to
> EXTERNAL (ssl client cert), did not change any SASL settings though;
> Attempted to connect to a different server in the network (via /server
> command) and apparently crashed during sasl

Thanks that makes sense. If you use /server make sure you do `/server freenode` for example, NEVER `/server chat.freenode.net`.
Comment 16 Patrick Griffis 2015-09-14 13:39:39 UTC 
Fixed upstream in https://github.com/hexchat/hexchat/commit/9c5f5770023b2dc07ffaa2f6cdcab365b6306894

The real solution to your problem would be adding more servers to the specific network though, I overlooked you wanted to jump servers, this can only work if hexchat knows which network a server belongs to.