Source: libsoup3 Version: 3.2.0-1 Severity: important Forwarded: https://gitlab.gnome.org/GNOME/libsoup/-/issues/302
Dear Maintainer, libsoup3 sometimes runs into a segmentation fault when using HTTP2 that can be worked around by forcing HTTP1 usage with the environment variable SOUP_FORCE_HTTP1=1 Logs will show the following type of warnings: libsoup-http2-WARNING **: 18:32:30.072: (../http2/soup-client-message-io-http2.c:410):io_read: runtime check failed: (io->in_callback == 0) before running into a segmentation fault. Thank you for your work on maintaining libsoup3 and especially your work on the recent transition! -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64, i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled