Bug#784112: /usr/sbin/saslauthd: saslauthd segfaults

2015-05-12 Thread Thomas Kupka
are there other factors at play that you can identify? > > > On 05/12/15 11:08 +0200, Thomas Kupka wrote: > >> I have changed the backend to pam and had no segfaults for the last 3 >> days. >> Seem like only the shadow backend has this issue. >> >> On Fri, May

Bug#784112: /usr/sbin/saslauthd: saslauthd segfaults

2015-05-12 Thread Thomas Kupka
I have changed the backend to pam and had no segfaults for the last 3 days. Seem like only the shadow backend has this issue. On Fri, May 8, 2015 at 9:10 AM, Thomas Kupka wrote: > > On Wed, 6 May 2015 09:10:15 -0500 Dan White wrote: > > > Can you get a backtrace from the core

Bug#784112: Fwd: Bug#784112: /usr/sbin/saslauthd: saslauthd segfaults

2015-05-08 Thread Thomas Kupka
is urge to change it. Thomas On Wed, May 6, 2015 at 4:10 PM, Dan White wrote: > On 05/03/15 10:24 +0200, Thomas Kupka wrote: > >> Package: sasl2-bin >> Version: 2.1.26.dfsg1-13 >> Severity: important >> File: /usr/sbin/saslauthd >> >> Dear Maintainer, >>

Bug#784112: /usr/sbin/saslauthd: saslauthd segfaults

2015-05-03 Thread Thomas Kupka
Package: sasl2-bin Version: 2.1.26.dfsg1-13 Severity: important File: /usr/sbin/saslauthd Dear Maintainer, since upgrading to Jessie, all saslauthd processes segfault on a multiple daily basis: May 3 06:26:12 mail kernel: [22739.740552] saslauthd[763]: segfault at 0 ip 7faffd5d8c8a sp 000