mutt-org crashed with SIGSEGV

Bug #965772 reported by Matt Zimmerman
70
This bug affects 10 people
Affects Status Importance Assigned to Milestone
mutt
Fix Released
Unknown
mutt (Ubuntu)
Confirmed
Medium
Vibhav Pant

Bug Description

I've been seeing this for a while, and it's still happening on current Precise.

It seems to happen when I'm reading mail in one mailbox, and mutt notifies me there is new mail in another mailbox. When I try to switch to the mailbox with new mail, I get a crash at the "Fetching message headers..." display (which normally goes by so quickly I don't even see it).

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mutt 1.5.21-5ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Mon Mar 26 15:27:51 2012
ExecutablePath: /usr/bin/mutt-org
ProcCmdline: mutt
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
 PATH=(custom, user)
 TERM=xterm
 LC_COLLATE=C
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mutt
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: mutt-org crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-04 (22 days ago)
UserGroups: adm admin audio cdrom dialout fuse kvm libvirtd lpadmin plugdev sambashare video

Related branches

Revision history for this message
Matt Zimmerman (mdz) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mx_update_context (ctx=0xfc0710, new_messages=<optimized out>) at ../mx.c:1650
 imap_read_headers (idata=0x2a44500, msgbegin=<optimized out>, msgend=5) at ../../imap/message.c:386
 imap_open_mailbox (ctx=0xfc0710) at ../../imap/imap.c:756
 mx_open_mailbox (path=<optimized out>, flags=0, pctx=0x0) at ../mx.c:681
 mutt_index_menu () at ../curs_main.c:1186

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in mutt (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Matt Zimmerman (mdz)
description: updated
visibility: private → public
Revision history for this message
Matt Zimmerman (mdz) wrote :

mx.c:1650 in the (patched) source seems to refer to the comment preceding the declaration of mx_update_context. It's pretty safe to say the crash didn't actually occur on that line. ;-)

When this happens, relaunching mutt and opening the same mailbox always works fine. It's only after the notification of new messages that the crash occurs.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mutt (Ubuntu):
status: New → Confirmed
Changed in mutt:
status: Unknown → Fix Released
Revision history for this message
Ben Williams (benw) wrote :

What's needed is the more recent patch from the upstream bug. I linked a bzr branch wherein I applied the newer patch. I've never submitted a patch to lp before, not sure if I'm doing this right.

Revision history for this message
Vibhav Pant (vibhavp) wrote :
Changed in mutt (Ubuntu):
assignee: nobody → Vibhav Pant (vibhavp)
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "mutt_1.5.21-5ubuntu3.debdiff" of this bug report has been identified as being a patch in the form of a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Revision history for this message
Matt Zimmerman (mdz) wrote :

Thanks for the patch! I see this crash pretty regularly.

Revision history for this message
Brian Murray (brian-murray) wrote :

The upstream mutt bug reporter contains a comment regarding the following Debian bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537694

That bug in Debian is fixed by the patch, debian/patches/upstream/537694-segv-imap-headers.patch, which is included in the Ubuntu package.

Oh, I see now Debian has the first patch from the upstream bug which doesn't seem to work.

Revision history for this message
Brian Murray (brian-murray) wrote :

I've reopened the debian bug regarding this issue as it would be good to have upstream fix their patch.

@Vibhav - your don't see to have used quilt properly in your debdiff as imap/message.c is still showing as being modified and your patch hasn't been added to the series file (debain/patches/series). Additionally, the original not work patch for this would need to be removed from the package too. I'll go ahead and take of these things.

Revision history for this message
Brian Murray (brian-murray) wrote :

Actually, there is a patch in debian that does cover this bug (well at least the upstream one like this) and its in version 1.5.21-5:

    + 584138-mx_update_context-segfault.patch: fix a segfault due to holes in
      IMAP headers, 537694-segv-imap-headers.patch is removed as part of this
      fix (Closes: 584138)

no longer affects: mutt (Debian)
Revision history for this message
Sebastien Bacher (seb128) wrote :

@Matt: is there any chance you could try to debdiff there and see if that fixes the issue for you,sponsor the update if it does?

@Brian: right, that patch is applied so it seems not enough, the upstream bug points to http://dev.mutt.org/trac/changeset/0e4f1782ea2e which is what the debdiff seems to include

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 965772] Re: mutt-org crashed with SIGSEGV

On Mon, Jun 04, 2012 at 03:06:38PM -0000, Sebastien Bacher wrote:
> @Matt: is there any chance you could try to debdiff there and see if
> that fixes the issue for you,sponsor the update if it does?

I am running with the patch from comment #8 now. I don't have a reproducer,
but will watch for a while and see if the bug recurs.

--
 - mdz

Revision history for this message
Matt Zimmerman (mdz) wrote :

I just got a similar looking crash while running with the patch from comment #8. :-/

apport won't report it because it's an obsolete package, but based on the user-visible symptoms I think it's a similar problem.

Revision history for this message
Brian Murray (brian-murray) wrote :

There is a setting to override the obsolete package check:

    # check obsolete packages
    if report['ProblemType'] == 'Crash' and \
        'APPORT_IGNORE_OBSOLETE_PACKAGES' not in os.environ:

Revision history for this message
Matt Zimmerman (mdz) wrote :

On Wed, Jun 20, 2012 at 05:46:28PM -0000, Brian Murray wrote:
> There is a setting to override the obsolete package check:
>
> # check obsolete packages
> if report['ProblemType'] == 'Crash' and \
> 'APPORT_IGNORE_OBSOLETE_PACKAGES' not in os.environ:

Yes, and I tried to use it, but it didn't work for me (anymore). I've used
it many times successfully in the past, e.g. by running
APPORT_IGNORE_OBSOLETE_PACKAGES=1 apport-cli <path to .crash file>.

--
 - mdz

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Given that there is still debate about the patch, I'm not sure there is anything for ubuntu-sponsors to do at this point. Perhaps upstream should be involved before we upload something?

Revision history for this message
Bryce Harrington (bryce) wrote :

Agreed; unsubscribing sponsors for now. Resubscribe once there's consensus on a solution.

Revision history for this message
Joey Stanford (joey) wrote :

I suspect this may also be a dup of open bug #666286 and open bug #861056

I found these after I had this same crash today. I can force Mutt to crash via a different mechanism though, via a notmuch-mutt call and doing a search for a popular word.

tags: added: saucy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.