Bug 674271
| Summary: | SIGSEGV when browsing pop account | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Stanislaw Gruszka <sgruszka> | ||||||||
| Component: | mutt | Assignee: | jpacner | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Zachar <lzachar> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 6.1 | CC: | jherrman, ovasik, tlavigne | ||||||||
| Target Milestone: | rc | Keywords: | Patch | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| 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.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-07-28 09:01:24 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 947782 | ||||||||||
| Attachments: |
|
||||||||||
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://..." . 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. 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 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. 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. Patch did not fix the problem, see: https://bugzilla.redhat.com/show_bug.cgi?id=690409#c6 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.
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 (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. 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). 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 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 |
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