Description of problem: From time to time when going through the cache mutt segfaults. I've included a core: Core was generated by `mutt'. Program terminated with signal 11, Segmentation fault. #0 mx_update_context (ctx=0x23cc370, new_messages=<optimized out>) at mx.c:1542 1542 h->security = crypt_query (h->content); Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.6-3.fc15.x86_64 cyrus-sasl-lib-2.1.23-16.fc15.x86_64 cyrus-sasl-md5-2.1.23-16.fc15.x86_64 cyrus-sasl-plain-2.1.23-16.fc15.x86_64 db4-4.8.30-3.fc15.x86_64 gnutls-2.10.5-1.fc15.x86_64 keyutils-libs-1.2-7.fc15.x86_64 krb5-libs-1.9-7.fc15.x86_64 libcom_err-1.41.14-2.fc15.x86_64 libgcc-4.6.0-9.fc15.x86_64 libgcrypt-1.4.6-1.fc15.x86_64 libgpg-error-1.9-2.fc15.x86_64 libidn-1.19-2.fc15.x86_64 libselinux-2.0.99-4.fc15.x86_64 libtasn1-2.7-2.fc15.x86_64 ncurses-libs-5.8-2.20110319.fc15.x86_64 nss-mdns-0.10-9.fc15.x86_64 nss-softokn-freebl-3.12.10-1.fc15.x86_64 openssl-1.0.0d-1.fc15.x86_64 tokyocabinet-1.4.46-2.fc15.x86_64 zlib-1.2.5-3.fc15.x86_64 (gdb) bt #0 mx_update_context (ctx=0x23cc370, new_messages=<optimized out>) at mx.c:1542 #1 0x0000000000493c1e in imap_read_headers (idata=0x23ad1a0, msgbegin=<optimized out>, msgend=27) at message.c:377 #2 0x0000000000491583 in imap_open_mailbox (ctx=0x23cc370) at imap.c:756 #3 0x0000000000442bb5 in mx_open_mailbox (path=<optimized out>, flags=0, pctx=0x0) at mx.c:661 #4 0x0000000000421b1f in mutt_index_menu () at curs_main.c:1161 #5 0x00000000004074f2 in main (argc=1, argv=<optimized out>) at main.c:1020 (gdb) p h $1 = (HEADER *) 0x0
Created attachment 510930 [details] core
I suppose you have mutt-1.5.21-5.fc15 installed. This failure seems to be caused by wrong index counting when a fetch respond is skipped and has been already fixed in Fedora Rawhide (http://koji.fedoraproject.org/koji/buildinfo?buildID=250846) and upstream (http://dev.mutt.org/trac/changeset/0e4f1782ea2e). I'm going to fix this in already released versions very soon, too. Until then you can test the Rawhide version mentioned above.
mutt-1.5.21-6.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mutt-1.5.21-6.fc15
Package mutt-1.5.21-6.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mutt-1.5.21-6.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/mutt-1.5.21-6.fc15 then log in and leave karma (feedback).
*** Bug 719215 has been marked as a duplicate of this bug. ***
mutt-1.5.21-6.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/mutt-1.5.21-6.fc14
(In reply to comment #2) > I suppose you have mutt-1.5.21-5.fc15 installed. > This failure seems to be caused by wrong index counting when a fetch respond is > skipped and has been already fixed in Fedora Rawhide > (http://koji.fedoraproject.org/koji/buildinfo?buildID=250846) and upstream > (http://dev.mutt.org/trac/changeset/0e4f1782ea2e). > > I'm going to fix this in already released versions very soon, too. Until then > you can test the Rawhide version mentioned above. Hi Jan, Just so I'm understanding correctly, how is that different than the fix in bug 676074? They both cite the same patches and upstream Trac bugs
(In reply to comment #7) > Hi Jan, > > Just so I'm understanding correctly, how is that different than the fix in bug > 676074? They both cite the same patches and upstream Trac bugs Hi James, generally this bug was caused by more unusual events, which led to the same segmentation fault. The upstream bug contains several versions of patches and this is the last one which fixes the most of problematic events (patch in bug #676074 doesn't handle all of them) and has been accepted by upstream.
(In reply to comment #8) > (In reply to comment #7) > > Hi Jan, > > > > Just so I'm understanding correctly, how is that different than the fix in bug > > 676074? They both cite the same patches and upstream Trac bugs > > Hi James, > generally this bug was caused by more unusual events, which led to the same > segmentation fault. The upstream bug contains several versions of patches and > this is the last one which fixes the most of problematic events (patch in bug > #676074 doesn't handle all of them) and has been accepted by upstream. Thanks for the explanation! I've yet to have another segfault but I've enabled cores just in case.
mutt-1.5.21-6.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
mutt-1.5.21-6.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 722984 has been marked as a duplicate of this bug. ***