On Wed, 20 Apr 2022 09:43:56 -0400 Steven Rostedt <rost...@goodmis.org> wrote:
> I just tested on my laptop which also has hexchat 2.16 (same version), and > it connects to my server's bip proxy just fine. I figured out the problem. It appears that my upgrade messed something up with pulseaudio, and caused anything to make a sound to not work. I believe what happened was when I connected to my bip server, it "replayed" all my messages which triggers beeps and alerts from hexchat. As my sound application (pulseaudio?) was messed up, it just hung at playing the sounds. Note, in trying to fix the sound issues, I uninstalled ekiga (which is no longer supplied by debian), removing sound files that I had hexchat using. After doing that, hexchat no longer locked up, but just gave me a ton of error messages saying that it could not find the sound files. It appears that xchat did not get stuck with the sounds (must be doing a better job at checking error codes or something), that it did not lock up due to it when connecting to my bip server. Feel free to close this bug, but you may want to look at the error handling of playing sounds. -- Steve
