Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

2023-01-25 Thread Sebastian Reichel
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 > > ¹

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

2023-01-24 Thread Martin
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

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

2023-01-17 Thread Sebastian Reichel
Hi, On Sat, 14 Jan 2023 21:53:59 + Martin wrote: > 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. I just got the

Bug#1028192: libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call

2023-01-13 Thread Martin
Control: clone -1 -2 Control: reassign -2 libproxy1v5 0.4.18-1 Control: retitle -2 libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call This is the backtrace with a debian.org account: (gdb) bt #0 read_encoded_value_with_base(unsigned char, _Unwind_Ptr, unsigned char const*, _Unwind_Ptr*)