headers
Mutt | 1 Jun 06:22

Re: [Mutt] #2883: mutt gets confused when a message disappears from

#2883: mutt gets confused when a message disappears from a maildir
-------------------------+--------------------------------------------------
  Reporter:  myon        |       Owner:  mutt-dev
      Type:  defect      |      Status:  closed  
  Priority:  minor       |   Milestone:  1.6     
 Component:  mutt        |     Version:          
Resolution:  worksforme  |    Keywords:          
-------------------------+--------------------------------------------------
Changes (by brendan):

  * status:  new => closed
  * resolution:  => worksforme

Old description:

> {{{
> ----- Forwarded message from Mike O'Connor <stew <at> vireo.org> -----
>
> Date: Wed, 18 Apr 2007 18:30:12 -0400
> From: Mike O'Connor <stew <at> vireo.org>
> Reply-To: Mike O'Connor <stew <at> vireo.org>, 419946 <at> bugs.debian.org
> To: Debian Bug Tracking System <submit <at> bugs.debian.org>
> Subject: Bug#419946: mutt gets confused when a message dissapears from a
>         maildir
>
> Package: mutt
> Version: 1.5.13-3
> Severity: normal
>
> I use offlineimap to keep multiple computers in sync with a remote
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 06:31

Re: [Mutt] #2902: Segmentation fault with IMAP/"The message index

#2902: Segmentation fault with IMAP/"The message index is incorrect. Try reopening
the mailbox."
------------------------+---------------------------------------------------
  Reporter:  neteler    |       Owner:  brendan
      Type:  defect     |      Status:  closed 
  Priority:  major      |   Milestone:  1.6    
 Component:  IMAP       |     Version:  1.5.16 
Resolution:  duplicate  |    Keywords:         
------------------------+---------------------------------------------------
Changes (by brendan):

  * status:  started => closed
  * resolution:  => duplicate

Old description:

> Mutt regularly crashes for me. I am using an IMAP box (Microsoft IMAP
> server), in parallel also thunderbird is listening to auto-filter
> selected messages into IMAP folders. This happens:
>

> {{{
> ---Mutt: imap://neteler <at> ntmail/INBOX [Msgs:1126 New:169 30M]---(reverse-
> date-received/date)------(3%)---
> Sorting mailbox...
> ---Type <return> to continue, or q <return> to quit---
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 182894227392 (LWP 9617)]
> 0x000000000047c3c9 in imap_cache_del (idata=0x6035d0, h=0x8aeba0) at
> message.c:919
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 06:33

Re: [Mutt] #2938: mutt freezes some times when accessing imap

#2938: mutt freezes some times when accessing imap folders or messages
--------------------------+-------------------------------------------------
  Reporter:  b.macdonald  |       Owner:  brendan 
      Type:  defect       |      Status:  accepted
  Priority:  major        |   Milestone:  1.6     
 Component:  IMAP         |     Version:          
Resolution:               |    Keywords:          
--------------------------+-------------------------------------------------

Old description:

> Mutt sometimes hangs when fetching a message, or opening a folder
> while fetching headers from an imap server. The imap server is Cyrus
> IMAP4 2.2.12-Invoca-RPM-2.2.12-8.1.RHEL4. This happens also with mutt
> 1.5.12 on one machine, as well as with mutt 1.5.13. This happens
> occasionally,
> not that often, but enough to be frustrating since mutt has to be
> restarted and
> changes to the mail folder are lost. Several times a day. Mutt won't
> respond except for ctl-Z to stop it, then the mutt process must be
> killed. In one case I collected a debug log from mutt -d, which showed
> that mutt has frozen part way through downloading an attachment. No
> error messages are given, the log simply stops part way through
> outputing the attachment to the log file.
>
> Well I'm not sure this is mutt or cyrus imapd but not sure how to tell
> the difference and the imap server is not accessible to me.

New description:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 06:38

Re: [Mutt] #3028: mutt segfaults while moving messages from gmail

#3028: mutt segfaults while moving messages from gmail
-------------------------------+--------------------------------------------
  Reporter:  michele.zaffalon  |       Owner:  brendan       
      Type:  defect            |      Status:  started       
  Priority:  major             |   Milestone:  1.6           
 Component:  IMAP              |     Version:  1.5.18        
Resolution:                    |    Keywords:  duplicate 2902
-------------------------------+--------------------------------------------

Old description:

> When moving messages from my Gmail IMAP account (usually to
> [GMAil]/Trash, I may have seen it also when copying to local folders),
> both mutt 1.5.16 from the stable OpenBSD 4.2 and 1.5.17 from the
> snapshots segfault.
> Only 1.5.17 was compiled with --enable-debug and -O0 -g (thanks, Stuart
> Henderson).
>
> michele$ mutt -v
> Mutt 1.5.17 (2007-11-01)
> Copyright (C) 1996-2007 Michael R. Elkins and others.
> Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
> Mutt is free software, and you are welcome to redistribute it
> under certain conditions; type `mutt -vv' for details.
>
> System: OpenBSD 4.2 (i386)
> ncurses: ncurses 5.2.20010224 (compiled with 5.2)
> libiconv: 1.9
> hcache backend: qdbm 1.8.75
> Compile options:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 06:39

Re: [Mutt] #3041: imap fetch segfault

#3041: imap fetch segfault
---------------------+------------------------------------------------------
  Reporter:  chrisl  |       Owner:  brendan       
      Type:  defect  |      Status:  closed        
  Priority:  major   |   Milestone:  1.6           
 Component:  IMAP    |     Version:                
Resolution:  fixed   |    Keywords:  duplicate 2902
---------------------+------------------------------------------------------
Changes (by brendan):

  * status:  started => closed
  * resolution:  => fixed

Old description:

> Hello,
>
> I am getting random segment fault during imap fetching from the outlook
> server.
>
> I take a look at the the core dump.
> {{{
> Program terminated with signal 11, Segmentation fault.
> #0  0x00000000004a3a3f in imap_cmd_step (idata=0x7c31a0) at command.c:558
> 558           if (h && h->active && h->index+1 == msgno)
> (gdb) bt
> #0  0x00000000004a3a3f in imap_cmd_step (idata=0x7c31a0) at command.c:558
> #1  0x00000000004a9c50 in imap_read_headers (idata=0x7c31a0,
> msgbegin=0, msgend=14320) at message.c:256
> #2  0x000037f000000000 in ?? ()
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 06:40

Re: [Mutt] #3236: mutt: should use /var/tmp for mail drafts by default

#3236: mutt: should use /var/tmp for mail drafts by default
-------------------------------+--------------------------------------------
  Reporter:  antonio <at> dyne.org  |       Owner:  mutt-dev
      Type:  enhancement       |      Status:  new     
  Priority:  minor             |   Milestone:          
 Component:  mutt              |     Version:          
Resolution:                    |    Keywords:          
-------------------------------+--------------------------------------------

Comment(by Derek Martin):

 {{{

 This is basically a system failure; data integrity can not be
 guaranteed regardless.

 If you don't want mutt to use /tmp by default, set $TMPDIR before
 starting Mutt, or set Mutt's tmpdir in your muttrc.  There's no need
 for this patch.  Please close this bug.
 }}}

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3236#comment:>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Derek Martin | 1 Jun 06:40
Gravatar

Re: [Mutt] #3236: mutt: should use /var/tmp for mail drafts by

>  This behaviour can cause loss of data, e.g. when the laptop dies or
>  turns itself off due to low power; the user might not have a chance
>  to commit the temporary mail draft s/he was working on to
>  non-volatile storage.

This is basically a system failure; data integrity can not be
guaranteed regardless.

If you don't want mutt to use /tmp by default, set $TMPDIR before
starting Mutt, or set Mutt's tmpdir in your muttrc.  There's no need
for this patch.  Please close this bug.
Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 06:40

Re: [Mutt] #3143: Segmentation fault in index menu with IMAP account

#3143: Segmentation fault in index menu with IMAP account
--------------------------+-------------------------------------------------
  Reporter:  debarshiray  |       Owner:  brendan       
      Type:  defect       |      Status:  closed        
  Priority:  major        |   Milestone:  1.6           
 Component:  IMAP         |     Version:  1.5.18        
Resolution:  fixed        |    Keywords:  duplicate 2902
--------------------------+-------------------------------------------------
Changes (by brendan):

  * status:  started => closed
  * resolution:  => fixed

Old description:

> Mutt 1.5.18 (2008-05-17), used with GMail's IMAP, encounters a
> segmentation fault in the index menu if the indicator is moved after a
> selected folder is kept idle for sometime (< 5 minutes). I have set
> imap_keepalive to 240.
>
> Mutt was configured with the following flags on Fedora Core 5 i386
> system:
> --prefix=/u/debray --enable-pgp --enable-smime --enable-pop --enable-imap
> --enable-smtp --enable-hcache --enable-exact-address --enable-locales-fix
> --with-ssl --disable-external-dotlock
>
> A bit of playing with GDB gave me the following.
>
> {{{
> Breakpoint 1, cmd_handle_fatal (idata=0x9288cf8) at command.c:368
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 06:42

Re: [Mutt] #3152: mutt crashes by trying to display the list of

#3152: mutt crashes by trying to display the list of mailboxes the second time
---------------------+------------------------------------------------------
  Reporter:  Ulrich  |       Owner:  mutt-dev
      Type:  defect  |      Status:  new     
  Priority:  major   |   Milestone:  1.6     
 Component:  IMAP    |     Version:  1.5.18  
Resolution:          |    Keywords:          
---------------------+------------------------------------------------------
Changes (by brendan):

  * version:  => 1.5.18

Old description:

> {{{
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb7c318e0 (LWP 14231)]
> 0x080e17b4 in ?? ()-  2 scholzuh emld
> (gdb) backtrace-xr-x 11 scholzuh emld
> #0  0x080e17b4 in ?? () scholzuh emld
> #1  0x08052c2c in ?? () scholzuh emld
> #2  0x08053272 in ?? () scholzuh emld
> #3  0x08070d26 in ?? () scholzuh emld
> #4  0x08064ec8 in ?? () scholzuh emld
> #5  0x080650bf in ?? () scholzuh emld
> #6  0x08069337 in ?? () scholzuh emld
> #7  0x08085600 in ?? () scholzuh emld
> #8  0xb7d1d685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6/
> #9  0x0804ce71 in ?? () scholzuh emld
> }}}
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 07:01

Re: [Mutt] #3145: atoi() is not safe (undefined behavior if value

#3145: atoi() is not safe (undefined behavior if value is not representable)
---------------------+------------------------------------------------------
  Reporter:  vinc17  |       Owner:  pdmef     
      Type:  defect  |      Status:  started   
  Priority:  major   |   Milestone:  1.6       
 Component:  mutt    |     Version:  1.5.18    
Resolution:          |    Keywords:  atoi patch
---------------------+------------------------------------------------------

Comment(by brendan):

 This patch looks quite nice to me. Please apply it.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3145#comment:7>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |

Gmane