Bug#1009891: hexchat locks up hard when connecting to bip server
On Wed, 20 Apr 2022 09:43:56 -0400 Steven Rostedt 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
Bug#1009891: hexchat locks up hard when connecting to bip server
On Wed, 20 Apr 2022 09:43:56 -0400 Steven Rostedt wrote: > I am running the latest 5.17.3 (vanilla stable kernel build, with no > modifications) on my workstation, and a 5.15 debian kernel on my laptop. > That shouldn't affect anything, but you never know. I can reboot my > workstation to an older kernel and see if that makes any difference. I rebooted to a 5.10 Debian kernel and it still has the same lockup. Strange that it works on my laptop but not my workstation. Oh, and xchat can connect to the bip proxy without issue. As a workaround, I'm currently just using xchat on my workstation instead of hexchat. -- Steve
Bug#1009891: hexchat locks up hard when connecting to bip server
On Wed, 20 Apr 2022 14:05:23 +0900 Marc Dequènes (duck) wrote: > Quack Seven, > > I'm involved with bip packaging and upstream and we wondered what > version of bip you are using. Did you upgrade bip recently? Actually I did. I updated both my server with bip and my workstation with hexchat at the same time. > We have yet no reason to think that it could be triggered by a bug in > bip, just checking. Clearly hexchat should behave better anyway. > > Can you reproduce this problem by connecting directly to the IRC server? No, the problem does not exist when connecting directly to my bip server. 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 am running the latest 5.17.3 (vanilla stable kernel build, with no modifications) on my workstation, and a 5.15 debian kernel on my laptop. That shouldn't affect anything, but you never know. I can reboot my workstation to an older kernel and see if that makes any difference. -- Steve
Bug#1009891: hexchat locks up hard when connecting to bip server
Quack Seven, I'm involved with bip packaging and upstream and we wondered what version of bip you are using. Did you upgrade bip recently? We have yet no reason to think that it could be triggered by a bug in bip, just checking. Clearly hexchat should behave better anyway. Can you reproduce this problem by connecting directly to the IRC server? Regards. \_o< -- Marc Dequènes
Bug#1009891: hexchat locks up hard when connecting to bip server
Package: hexchat Version: 2.16.0-4+b2 Severity: grave Justification: renders package unusable Dear Maintainer, When connecting hexchat to my bip server it locks up hard. It use to work fine, until I upgraded to 2.16. The bip server connects to OFTC, and when I connect to it, the application just stops. That is the screen is blank, none of the buttons react to anything. When I do: ps -efL | grep hexchat: rostedt 850968458509 04 22:19 ?00:00:00 hexchat rostedt 850968458521 04 22:19 ?00:00:00 hexchat rostedt 850968458522 04 22:19 ?00:00:00 hexchat rostedt 850968458550 04 22:19 ?00:00:00 hexchat Then look at: $ cat /proc/8509/wchan futex_wait_queue $ cat /proc/8521/wchan do_sys_poll $ cat /proc/8522/wchan do_sys_poll $ cat /proc/8550/wchan do_sys_poll It appears that a thread holds a futex (pthread_mutex?) and is then doing a poll() system call and never returning. The main thread is then stuck doing nothing, and the application hangs. The only way to stop it is to send a signal to it. It connects to other servers fine, just not my bip proxy. But it use to work before this upgrade. I do not remember what the older version was, but I upgrade my system once a month, so whatever the debian version of it was back in March was the last version that worked for me. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (1000, 'stable-security'), (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.3-custom (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages hexchat depends on: ii hexchat-common 2.16.0-4 ii libc62.33-7 ii libcanberra0 0.30-10 ii libdbus-glib-1-2 0.112-2 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libglib2.0-0 2.72.0-1+b1 ii libgtk2.0-0 2.24.33-2 ii libpango-1.0-0 1.50.6+ds-2 ii libssl1.11.1.1k-1+deb11u2 ii libx11-6 2:1.7.5-1 Versions of packages hexchat recommends: ii ca-certificates 20211016 ii hexchat-lua 2.16.0-4+b2 ii hexchat-perl 2.16.0-4 ii hexchat-plugins 2.16.0-4+b2 ii hexchat-python3 2.16.0-4+b2 ii libglib2.0-bin 2.72.0-1+b1 Versions of packages hexchat suggests: ii hexchat-otr 0.2.2-3 pn unifont -- no debconf information
