On Sun, Jun 25, 2017 at 07:50:00PM +, Antonio Radici wrote:
> On Sun, Jun 25, 2017 at 12:14:29PM -0400, Peter Colberg wrote:
> > Control: reopen -1
> > Control: found -1 1.7.2-1
> > Control: tags -1 stretch
> >
> > > On 2017-06-24 18:49:55, Antonio Radici wrote:
> > > > On Mon, Sep 12, 2016 at
On Sun, Jun 25, 2017 at 12:14:29PM -0400, Peter Colberg wrote:
> Control: reopen -1
> Control: found -1 1.7.2-1
> Control: tags -1 stretch
>
> > On 2017-06-24 18:49:55, Antonio Radici wrote:
> > > On Mon, Sep 12, 2016 at 04:51:21PM +0200, Sebastian Ramacher wrote:
> > >
> > > I believe this has b
Control: reopen -1
Control: found -1 1.7.2-1
Control: tags -1 stretch
> On 2017-06-24 18:49:55, Antonio Radici wrote:
> > On Mon, Sep 12, 2016 at 04:51:21PM +0200, Sebastian Ramacher wrote:
> >
> > I believe this has been solved in 1.8.3+neomutt20170609-1; I've removed all
> > pager.c patches and
On Mon, Sep 12, 2016 at 04:51:21PM +0200, Sebastian Ramacher wrote:
> Package: mutt
> Version: 1.7.0-3
> Severity: normal
>
> Since the last update, I repeatedly get SIGSEGVs while going through some
> unseen
> mails in my inbox:
>
> Program terminated with signal SIGSEGV, Segmentation fault.
>
forcemerge 837601 837584
thanks
Same as #837601, it is high on my priority list as soon as I'm able to reproduce
it.
Package: mutt
Version: 1.7.0-3
Severity: normal
Since the last update, I repeatedly get SIGSEGVs while going through some unseen
mails in my inbox:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x55596b73f69a in update_index (menu=0x0, ctx=0x55596d883090, check=1,
oldcount=
6 matches
Mail list logo