Re: [Mutt] #3075: Segfault when viewing attachement

#3075: Segfault when viewing attachement Changes (by raorn): * version: => 1.5.18 -- Ticket URL:

Re: [Mutt] #3075: Segfault when viewing attachement

#3075: Segfault when viewing attachement Changes (by raorn): * cc: [EMAIL PROTECTED] (added) -- Ticket URL:

Re: [Mutt] #3075: Segfault when viewing attachement

#3075: Segfault when viewing attachement Changes (by Alexey I. Froloff <[EMAIL PROTECTED]>): * status: new => closed * resolution: => fixed Comment: (In [1e8ca708a52f]) Do not attempt to close invalid descriptors. Closes #3075 -- Ticket URL:

Re: [Mutt] #3067: PGP/MIME signatures incorrectly assigned

#3067: PGP/MIME signatures incorrectly assigned "Content-Disposition: inline" Changes (by brendan): * type: defect => enhancement * component: mutt => crypto Comment: I'm not sure I agree that the disposition should be attachment. Although the RFC doesn't specify one way or the other, t

Re: segfault in mx_update_context()

Yes, this is a pesky bug that I don't think we've quite tracked down yet. Looks like it's related to new messages getting announced when mutt isn't ready -- maybe when mutt is already in the process of parsing previously-announced new mail. On Saturday, 07 June 2008 at 15:33, Jukka Salmi wrote: >

[Mutt] #3075: Segfault when viewing attachement

#3075: Segfault when viewing attachement Mutt may catch a segfault when viewing an attachment with certain mailcap entry. Patch attached. -- Ticket URL: