Mutt often freezes in the "Sorting mailbox..." stage when opening an IMAP mailbox. It also often freezes when viewing a mailbox over IMAP (either the message header list or a message body). Reproducible: Always Steps to Reproduce: 1. Start mutt 2. Select an IMAP mailbox or 1. Start mutt 2. Select an IMAP mailbox 3. Browse messages in the mailbox Actual Results: Mutt freezes, sometimes for 15mins or more. Expected Results: Mutt shouldn't freeze. Thunderbird (for example) doesn't freeze when tested immediately after mutt freezes for the same mailboxes and IMAP server, so this doesn't seem to be due to a slow IMAP server. When frozen, top doesn't report any abnormal CPU usage for mutt. Mutt usually unfreezes eventually (when I have the patience to wait that long!). I'm using the IMAP header cache (muttrc contains "header_cache=[directory]"). However, I get similar behaviour with the header cache turned off. Things seem subjectively to have improved very slightly with the new mutt release which includes a new header cache patch. It also seems subjectively to be worse on a 2.4 kernel than on 2.6 (despite the fact that the machine running the 2.4 kernel is much faster than the one running 2.6). emerge info output (from the machine running the 2.4 kernel): Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.4.26-gentoo-r9 i686) ================================================================= System uname: 2.4.26-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/afs/C /etc/afs/afsws /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.tiscali.nl/gentoo/ ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp.easynet.nl/mirror/gentoo/ ftp://ftp6.uni-muenster.de/pub/linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d acpi afs alsa arts avi bash-completion berkdb bitmap-fonts bzlib cdr crypt cups divx4linux doc dvd emacs encode f77 fam fbcon foomaticdb fortran ftp gdbm gif gpm hardened icq imagemagick imap imlib jpeg kde kerberos libg++ libwww mad maildir mikmod mmx motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl pic png ppds python qt quicktime readline sasl sdl slang spell sse ssl svga tcpd tetex tiff truetype x86 xml xml2 xmms xv yahoo zlib linguas_en linguas_de"
Probably not a mutt problem, rather a networking issue. Try using tcpdump and/or ethereal to capture the packet stream when conversing with the imap server.
I have been experiencing this same issue. Since I AM the network engineer, I have verified that network issues are not the problem. bash-2.05b# emerge info output Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r4 i686) ================================================================= System uname: 2.6.9-gentoo-r4 i686 Intel(R) Pentium(R) 4 Mobile CPU 1.60GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.14.90.0.8-r1 Headers: sys-kernel/linux-headers-2.4.21-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=i686 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3 /env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /us r/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -mcpu=i686 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/dis tributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups encode f77 fam fooma ticdb fortran gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl slang spell ssl svga tcpd tiff truetype x86 xml2 x mms xv zlib"
Have you tried mutt with no patches ( vanilla use flag ) ? Maybe some patch is playing nasty. I use mutt in several different networks with imap servers and have no problem. I've always used mutt vanilla anyway. Cheers Ferdy
Since I have upgraded my kernel to 2.6.10-r4 mutt crashes my whole system. ): It used to work nice with 2.6.8-r13 kernel.
I experience the same problem (mutt locks some minutes when operating on IMAP mailboxes) since I upgraded from mutt-1.5.4-r1 to mutt-1.5.6-r5. I also tried to emerge the vanilla version, but no improvement. Anyway, I conclude it is _not_ the network connection...
I just have tested with gentoo-dev-sources 2.6.10-r6 and mutt still freezes my system. Network shouldn't be a prob, because the imap server is on the same machine.
do you have some kernel oopses/-panics or some information in dmesg? And what's about the mentioned USE="vanilla"? did you tried that?
Everybody says "it's not a networking issue" but nobody has given evidence of trying tcpdump or ethereal. Since we don't see this bug, you guys are going to need to do some debugging (ethereal, tcpdump, strace, ltrace, etc) and give us some clues. Until then, closing NEEDINFO
