Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Dear Laurent, dear Jeremy, der Iain, because I'm not sure, if you saw it: I uploaded libproxy 0.4.18-1.2 with Sebastians patch to DELAYED/5. You might like to do something different, therefore my headsup. Cheers
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Le vendredi, 27 janvier 2023, 17.50:40 h CET Martin a écrit : > Control: tags -1 + patch > > So far only good reports about the patch by Sebastian , > applied in experimental. From the St-Cergue BSP; could confirm that the crash is fixed by installing libproxy1v5 from experimental. Looking forward to getting this fixed in unstable! Best, OdyX signature.asc Description: This is a digitally signed message part.
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Control: tags -1 + patch So far only good reports about the patch by Sebastian , applied in experimental.
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Sorry, that went to the wrong bug report :-( Laurent, Jeremy, Iain, I hope you are OK with the upload to experimental! On 2023-01-25 15:11, Sebastian Reichel wrote: > [[PGP Signed Part:Undecided]] > Hi Martin, > > On Tue, Jan 24, 2023 at 10:50:52PM +, Martin wrote: >> Hi Sebastian, >> >> I wonder, if I should upload libproxy with your github patch¹ to >> experimental. Then people affected (or not affected) by the bug can test >> easily. Or you may upload, of course! :-) >> >> Cheers >> >> ¹ https://github.com/libproxy/libproxy/issues/199#issuecomment-1401124997 > > sure, feel free to upload it to experimental. FWIW I do not > understand the root cause of this issue. I'm a bit worried, > that the patch masks a security relevant bug. It would be great > if somebody with better C++ knowledge can look into this. > > The bug seems quite strange considering the segmentation fault is > happening due to the destruction of an empty vector from the standard > library and only in combination with glib-networking. > > FWIW long term the problem will be solved by glib-networking > removing the libproxy dependency: > > https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/205 > > Greetings, > > -- Sebastian > > [[End of PGP Signed Part]]
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Hi, On Thu, Jan 19, 2023 at 04:12:14PM +0100, Sebastian Reichel wrote: > On Wed, Jan 18, 2023 at 09:48:33PM +, 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
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Hi, On Wed, Jan 18, 2023 at 09:48:33PM +, Martin wrote: > Control: severity -1 grave > > Justification for grave: Crashes Gajim for some users. RC, IMHO. > > 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). -- Sebastian signature.asc Description: PGP signature
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Control: severity -1 grave Justification for grave: Crashes Gajim for some users. RC, IMHO. 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! Thank you!
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Control: severity -1 normal The problem disappeared magically for all users who reported it before. I assume, that there is a hidden bug in libproxy, that only appears in certain circumstances. Downgrading for now.
Bug#1028638: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Control: found -1 0.4.16-1 Control: notfound -1 0.4.15-15 I tried various versions of libproxy from snapshot.debian.org and could find the crash to be introduced by version 0.4.16-1 exactly.
