RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 674271 - SIGSEGV when browsing pop account
Summary: SIGSEGV when browsing pop account
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mutt
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: jpacner
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On:
Blocks: 947782
TreeView+ depends on / blocked
 
Reported: 2011-02-01 09:09 UTC by Stanislaw Gruszka
Modified: 2014-07-28 09:01 UTC (History)
3 users (show)

Fixed In Version: mutt-1.5.20-6.20091214hg736b6a.el6
Doc Type: Bug Fix
Doc Text:
Prior to this update, an internal hash referencing a specific subject in each envelope referenced a non-existent one. As a consequence, mutt terminated with a segmentation fault when the user attempted to synchronize mailbox after removing one or more messages in threaded mode. With this update, the subject hash updates correctly and the crash no longer occurs.
Clone Of:
Environment:
Last Closed: 2014-07-28 09:01:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
abrt.log (52.65 KB, text/plain)
2011-02-01 09:09 UTC, Stanislaw Gruszka 		no flags Details
proposed very simple patch (628 bytes, patch)
2011-06-06 11:54 UTC, Honza Horak 		no flags Details | Diff
mutt-fix.patch (2.43 KB, text/plain)
2011-10-02 19:12 UTC, Stanislaw Gruszka 		no flags Details
Show Obsolete (1) View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0945 0 normal SHIPPED_LIVE mutt bug fix update 2014-07-28 13:00:56 UTC

Description Stanislaw Gruszka 2011-02-01 09:09:51 UTC 
Created attachment 476338 [details]
abrt.log

Version-Release number of selected component (if applicable):
[root@dhcp-27-172 ~]# rpm -qa | grep mutt
mutt-1.5.20-2.20091214hg736b6a.el6.i686
mutt-debuginfo-1.5.20-2.20091214hg736b6a.el6.i686
[root@dhcp-27-172 ~]# rpm -qa | grep glibc
glibc-headers-2.12-1.7.el6.i686
glibc-debuginfo-2.12-1.7.el6.i686
glibc-common-2.12-1.7.el6.i686
glibc-devel-2.12-1.7.el6.i686
glibc-2.12-1.7.el6.i686
[root@dhcp-27-172 ~]# rpm -qa | grep tokyo
tokyocabinet-1.4.33-6.el6.i686
tokyocabinet-debuginfo-1.4.33-6.el6.i686
Comment 2 Stanislaw Gruszka 2011-02-01 09:19:16 UTC 
I think this happen in threaded mode when I delete some emails from thread and do sync-mailbox command ($ key). I had this only with "-f pops://..." .
Comment 3 RHEL Program Management 2011-02-01 16:48:40 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4 Honza Horak 2011-06-06 11:54:48 UTC 
Created attachment 503203 [details]
proposed very simple patch

Unfortunately, I'm not able to reproduce this failure, but I think this very easy patch should fix this failure and shouldn't bring another regression. 

I've submitted this patch to upstream to see what mutt developers think: http://dev.mutt.org/trac/ticket/3525
Comment 5 Stanislaw Gruszka 2011-06-10 11:47:12 UTC 
Jan, I'm not ignoring your patch, but I also can not reproduce bug currently on unpatched mutt. I'm not sure what make a difference, perhaps that before I had much more messages in the pop3 mbox (1500 > ) now I have about 400. I plan to post lots of emails to myself and check if could find the way to reproduce to confirm the fix.
Comment 6 RHEL Program Management 2011-07-06 01:37:56 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 7 Stanislaw Gruszka 2011-08-14 12:01:33 UTC 
Patch did not fix the problem, see:
https://bugzilla.redhat.com/show_bug.cgi?id=690409#c6
Comment 8 Stanislaw Gruszka 2011-10-02 19:12:25 UTC 
Created attachment 525954 [details]
mutt-fix.patch

I spent this Sunday afternoon on drinking kofola and debugging mutt. This is a result.

I wanted post patch to mutt-dev but ML is for subscribers only. I'm a bit reluctant to subscribe just to post one patch. Hopefully Honza, you can post it and do whatever needed to make it applied. Thanks.
Comment 9 Honza Horak 2011-10-04 16:05:04 UTC 
Thanks for a great job! 
I've forwarded your patch to upstream, let's wait what they say:
http://dev.mutt.org/trac/ticket/3525
Comment 13 Honza Horak 2013-06-27 11:43:53 UTC 
(In reply to Honza Horak from comment #9)
> I've forwarded your patch to upstream, let's wait what they say:
> http://dev.mutt.org/trac/ticket/3525

The patch was accepted upstream (http://dev.mutt.org/trac/changeset/6231) and is already applied in Fedora.
Comment 20 jpacner 2014-05-16 12:31:07 UTC 
Fixed in commit http://pkgs.devel.redhat.com/cgit/rpms/mutt/commit/?h=rhel-6.6&id=011263dbff90337a51aa840f40a299e2fc02d6de (build mutt-1.5.20-5.20091214hg736b6a.el6).
Comment 23 jpacner 2014-07-23 14:08:19 UTC 
List of patches present on mutt-1.5.20-6.20091214hg736b6a.el6:
http://pkgs.devel.redhat.com/cgit/rpms/mutt/commit/?h=rhel-6.6&id=011263dbff90337a51aa840f40a299e2fc02d6de
Comment 27 errata-xmlrpc 2014-07-28 09:01:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0945.html
Note You need to log in before you can comment on or make changes to this bug.