Bug 516210
| Summary: | mutt no longer works when connecting to a IMAP server | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Eric Goirand <eric.goirand> | ||||||
| Component: | mutt | Assignee: | Miroslav Lichvar <mlichvar> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 11 | CC: | ewan, mlichvar, pertusus | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-06-28 14:01:40 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Eric Goirand
2009-08-07 12:57:16 UTC
It seems to work fine here. Can you make a backtrace in gdb? Which mail server implementation is running on the server? Also mutt recompiled with debug might be useful. It is enabled by -d and the output is stored in ~/.muttdebug* (remove private information before attaching here). Can you please try package from this scratch build? http://koji.fedoraproject.org/koji/taskinfo?taskID=1605039 Miroslav, The IMAP server I'm using is cyrus-imapd-2.3.14-1.fc10.x86_64 . I installed mutt-1.5.20-1.20090814hg.fc11.x86_64 from the link you gave to me. I put in attachment file mutt.debug.tjz which contains .muttdebug0 (mutt -d 1) and .muttdebug1 (mutt -d 2). Each time mutt server stops at 99% and I need to kill it to stop it. Created attachment 357531 [details]
To extract, tar xvjf mutt.debug.tjz
Contains .muttdebug0, output of mutt -d 1, and .muttdebug1, output of mutt -d 2
It looks like it's caused by four messages for which the server returns "no longer exists". Unfortunately I couldn't reproduce it with cyrus-imapd here. Can you please attach gdb backtrace when it's hung? - install debuginfo package (http://koji.fedoraproject.org/koji/getfile?taskID=1605041&name=mutt-debuginfo-1.5.20-1.20090814hg.fc11.x86_64.rpm) - gdb /usr/bin/mutt pid - bt Created attachment 357714 [details]
gdb backtrace of mutt when mutt is blocked at 99% of mail headers
I installed mutt-debuginfo and performed the gdb backtrace when mutt is blocked at 99% of mail headers loading, file gdb-bt.txt is the output of it.
Ok, I think I have a fix for this, please try this build: http://koji.fedoraproject.org/koji/taskinfo?taskID=1611923 I installed mutt-1.5.20-1.20090814hg.fc11.1.x86_64 and mutt-debuginfo-1.5.20-1.20090814hg.fc11.1.x86_64 . I started mutt again and is killed by a segmentation fault : Fetching message headers... 3370/3378 (99%)Segmentation fault Upstream bug filed at http://dev.mutt.org/trac/ticket/3316 Hi Miroslav, Any news from the mutt upstream project ? I tried it with Fedora 12 and it has the same behavior, nothing changed :-(, I can no longer read my emails and still need to connect to a F10 machine to do that. Do you think I should change my IMAP server ? I don't understand what happens in it that creates the problem in Mutt. Would you have any insight of what could be wrong in it ? Maybe I can correct the problem in cyrus-imapd to solve the Mutt problem. Cheers, Eric. There were no updates yet. The problem is the "message * no longer exists" response. I think if the cyrus cache where the headers are stored was recreated, it would work again. Thanks to what you explained, I reconstructed the cyrus indexes of the user mailboxes with the following command for each ${user} :
# /usr/lib/cyrus-imapd/reconstruct -r user.${user}
Then I tried again mutt and it worked fine again :-).
Many thanks Miroslav, I think there is now a correct way to solve the problem every time.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |