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
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 forwa
Processing control commands:
> tags -1 + patch
Bug #1028638 [libproxy1v5] libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Added tag(s) patch.
--
1028638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
So far only good reports about the patch by Sebastian ,
applied in experimental.
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
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
netw
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
Processing control commands:
> severity -1 grave
Bug #1028638 [libproxy1v5] libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
Severity set to 'grave' from 'normal'
--
1028638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028638
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
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.
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.
10 matches
Mail list logo
