Hi, On Thu, Jan 19, 2023 at 04:12:14PM +0100, Sebastian Reichel wrote: > On Wed, Jan 18, 2023 at 09:48:33PM +0000, Martin wrote: > > Control: severity -1 grave > > > > Justification for grave: Crashes Gajim for some users. RC, IMHO.
If I understood it correctly libproxy is only used by glib networking code when not running GNOME. > > On 2023-01-17 21:56, Sebastian Reichel wrote: > > > I just got the new package through testing and now gajim segfaults > > > ony my system with stacktrace pointing to libproxy. So this is not > > > magically solved. > > > > :-( > > > > Could you check, if a downgrade to libproxy 0.4.15-15 helps? > > That certainly helps to find the bug! > > I tried downgrading libproxy1v5 and libproxy-tools to 0.4.15-15 and > glib-networking to 2.66.0. This did not change anything. > > With libproxy from testing gajim does work when being downgraded to > 1.5.4-1 (which requires also downgrading python3-nbxmpp to > 3.2.5-1 to be functional). This has been reported upstream: https://github.com/libproxy/libproxy/issues/199 Also these apparently describe the same bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970687 https://github.com/exaile/exaile/issues/737 Both workarounds mentioned in those bug reports (removing either /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so or /usr/lib/x86_64-linux-gnu/libproxy.so.1.0.0) fix the crash and gajim successfully connects. -- Sebastian
signature.asc
Description: PGP signature