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
Created attachment 1073141 [details] File: backtrace
Created attachment 1073142 [details] File: cgroup
Created attachment 1073143 [details] File: core_backtrace
Created attachment 1073144 [details] File: dso_list
Created attachment 1073145 [details] File: environ
Created attachment 1073146 [details] File: limits
Created attachment 1073147 [details] File: maps
Created attachment 1073148 [details] File: mountinfo
Created attachment 1073149 [details] File: namespaces
Created attachment 1073150 [details] File: open_fds
Created attachment 1073151 [details] File: proc_pid_status
Created attachment 1073152 [details] File: var_log_messages
Were you just using the SASL options in the network list?
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
(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`.
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.