I got more informations while putting my hands randomly on hexchat. This bug happens if the following conditions are satisfied: 1- Hexchat tries to connect to a server, gets a DNS answer, tries to contact the server ip and the server won't answer, but the connection attempt won't end either 2- The connection attempt is terminated manually (Server > Disconnect) 3- Another server is chosen and the connection is successful 4- (Not certain but seems in 90% of cases to be related) Hexchat receives a message which triggers a dbus notification Something makes me suspect that in this particular situation the notification method isn't handled correctly, resulting in dbus closing the connection and libdbus-glib killing hexchat
signature.asc
Description: This is a digitally signed message part
