Your message dated Mon, 26 Jan 2009 22:11:10 +0000
with message-id <[email protected]>
and subject line mutt: Segfault on IMAP folder list
has caused the Debian Bug report #462266,
regarding mutt: segfault when switching between IMAP folders
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
462266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462266
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 1.5.18-1
Severity: important


I'm trying to use mutt to access both my work IMAP account, and my gmail
account via IMAP.

This is possibly related to bug #462266, but I can't reproduce the crash
in the same way.

I have the following settings in my .muttrc:
mailboxes imaps://[email protected] imaps://[email protected]
set spoolfile=imaps://[email protected]/INBOX
set folder=imaps://[email protected]
set header_cache="/home/catlee/.mutt/headers"
set message_cachedir="/home/catlee/.mutt/messages"
set move="no"
set imap_passive="yes"

When I switch from my work account to gmail, things work ok (I hit 'c',
then tab twice, then select my gmail account).  But when I
try and switch back to my work account, mutt segfaults (I hit 'c',
then tab twice, segfault on the second tab).

I built a debug version of mutt so I could get a backtrace, which I have
included below.  idata->ctx is null, so the line 'state->new =
idata->ctx->new' is what causes the crash.

#0  0x000000000047ce5a in imap_mailbox_state (
    path=0x6e5810 "imaps://[email protected]/", state=0x7fff8adf7e30)
    at browse.c:233
#1  0x000000000040a77b in examine_mailboxes (menu=0x700680, 
    state=0x7fff8adf8bd0) at browser.c:445
#2  0x000000000040ae26 in _mutt_select_file (f=0x7fff8adf9240 "", flen=1024, 
    flags=2, files=0x0, numfiles=0x0) at browser.c:1151
#3  0x0000000000423e6e in _mutt_enter_string (buf=0x7fff8adf9240 "", 
    buflen=1024, y=46, x=14, flags=4, multiple=0, files=0x0, numfiles=0x0, 
    state=0x700410) at enter.c:569
#4  0x000000000041a5a7 in _mutt_get_field (field=0x7015d0 "Open mailbox: ", 
    buf=0x7fff8adf9240 "", buflen=1024, complete=36, multiple=0, files=0x0, 
    numfiles=0x0) at curs_lib.c:144
#5  0x000000000041a72e in _mutt_enter_fname (prompt=0x48be15 "Open mailbox", 
    buf=0x7fff8adf9240 "", blen=1024, redraw=0x713c30, buffy=1, multiple=0, 
    files=0x0, numfiles=0x0) at curs_lib.c:575
#6  0x000000000041d8bb in mutt_index_menu () at curs_main.c:1086
#7  0x0000000000435414 in main (argc=1, argv=0x7fff8adfa228) at main.c:999


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mutt depends on:
ii  libc6                    2.7-12          GNU C Library: Shared libraries
ii  libgdbm3                 1.8.3-3         GNU dbm database routines (runtime
ii  libgnutls26              2.2.5-1         the GNU TLS library - runtime libr
ii  libidn11                 1.8-2           GNU libidn library, implementation
ii  libncursesw5             5.6+20080531-1  Shared libraries for terminal hand
ii  libsasl2-2               2.1.22.dfsg1-20 Cyrus SASL - authentication abstra

Versions of packages mutt recommends:
ii  locales                       2.7-12     GNU C Library: National Language (
ii  mime-support                  3.43-1     MIME files 'mime.types' & 'mailcap
ii  postfix [mail-transport-agent 2.5.2-1    High-performance mail transport ag

-- no debconf information



--- End Message ---
--- Begin Message ---
As Steve noted, the problem is fixed in 1.5.19-1

Cheers
Antonio


--- End Message ---

Reply via email to