Your message dated Wed, 18 May 2022 13:28:16 -0600
with message-id <[email protected]>
and subject line Re: Bug#1009791: mutt: change-folder no longer selects next
folder with new mail
has caused the Debian Bug report #1009791,
regarding mutt: change-folder no longer selects next folder with new mail
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.)
--
1009791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009791
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 2.2.3-1
Severity: normal
I upgrade my Sid Unstable desktop daily. The upgrade from 2.1.4-1 to
2.2.3-1 breaks the change-folder action (normally bound to 'c').
Normally and up through mutt 2.1.4-1 (at least) typing 'c' would
prompt with the next mailbox that has new mail since the last time
mutt visited the folder. That allowed a set of mailboxes to be walked
through one after the other. The messages are seen. Then whether
mail is read or not read 'c' moves to another folder. Mutt will
prompt for a different folder with new mail. If new mail arrives in a
previously visited folder then it will once again become a candidate
for prompting with the change-folder action.
Starting with 2.2.3-1 the 'c' change-folder action now prompts with
the *previous folder always* and never prompts with any other folders.
It no longer selects a mailboxes folder with new mail. It prompts
with the previous folder even if no new mail has arrived there.
Effectively creating a situation where one toggles between two folders
endlessly.
I don't know why the previous folder is always selected. It's
possible that upon leaving the folder that mutt 2.2.3-1 modifies it in
some way causing it to appear new and therefore to be placed at the
top of the new mail folder list next change-folder action. I don't
know. That would be one possible way to create this behavior. But
whatever the root cause it breaks use of the 'c' change-folder action.
Note that this is separate from pressing space to rotate through the
mailboxes list manually. Yes it is always possible to spacebar
through all of the configured mailboxes manually. But that is very
tedious when a lot of mailboxes are configured. This is definitely a
regression from before when this prompted for a folder from the
configured mailboxes list that had new mail.
Downgrading to 2.1.4-1 and holding it works around this problem.
apt-get install mutt=2.1.4-1
apt-mark hold mutt
Thank you for maintaining Mutt in Debian.
Bob
-- Package-specific info:
Mutt 2.2.3 (2022-04-12)
Copyright (C) 1996-2022 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: Linux 5.16.0-6-amd64 (x86_64)
ncurses: ncurses 6.3.20211021 (compiled with 6.3)
libidn2: 2.3.2 (compiled with 2.3.2)
hcache backend: tokyocabinet 1.4.48
Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 11.2.0-19'
--with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-11
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--enable-libphobos-checking=release --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-11-uiwEqG/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-uiwEqG/gcc-11-11.2.0/debian/tmp-gcn/usr
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.2.0 (Debian 11.2.0-19)
Configure options: --build=x86_64-linux-gnu --prefix=/usr
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
'--infodir=${prefix}/share/info' --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
'--libdir=${prefix}/lib/x86_64-linux-gnu' --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
--with-mailpath=/var/mail --enable-compressed --enable-debug --enable-fcntl
--enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-pop
--enable-sidebar --enable-dotlock --disable-fmemopen --with-curses
--with-gnutls --with-gss --with-idn2 --with-mixmaster --with-sasl
--without-gdbm --without-bdb --without-qdbm --with-tokyocabinet
build_alias=x86_64-linux-gnu 'CFLAGS=-g -O2
-ffile-prefix-map=/build/mutt-Z2eSdv/mutt-2.2.3=. -fstack-protector-strong
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now'
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'
Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2
-ffile-prefix-map=/build/mutt-Z2eSdv/mutt-2.2.3=. -fstack-protector-strong
-Wformat -Werror=format-security
Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK
+USE_POP +USE_IMAP +USE_SMTP
-USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL -USE_GSASL +USE_GSS
+HAVE_GETADDRINFO
+HAVE_REGCOMP -USE_GNU_REGEX
+HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET
+HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_FUTIMENS
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME
-EXACT_ADDRESS -SUN_ATTACHMENT
+ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR
+HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_LIBIDN2 +HAVE_GETSID
+USE_HCACHE
+USE_SIDEBAR +USE_COMPRESSED +USE_INOTIFY
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
MIXMASTER="mixmaster"
To contact the developers, please mail to <[email protected]>.
To report a bug, please contact the Mutt maintainers via gitlab:
https://gitlab.com/muttmua/mutt/issues
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages mutt depends on:
ii libc6 2.33-7
ii libgnutls30 3.7.4-2
ii libgpg-error0 1.43-3
ii libgpgme11 1.16.0-1.2
ii libgssapi-krb5-2 1.19.2-2+b1
ii libidn2-0 2.3.2-2
ii libncursesw6 6.3-2
ii libsasl2-2 2.1.28+dfsg-3
ii libtinfo6 6.3-2
ii libtokyocabinet9 1.4.48-14
ii zlib1g 1:1.2.11.dfsg-4
Versions of packages mutt recommends:
ii libsasl2-modules 2.1.28+dfsg-3
ii locales 2.33-7
ii mailcap 3.70+nmu1
ii sensible-utils 0.0.17
Versions of packages mutt suggests:
ii aspell 0.60.8-4
ii ca-certificates 20211016
ii gnupg 2.2.27-3
ii ispell 3.4.05-1
ii openssl 1.1.1n-1
ii postfix [mail-transport-agent] 3.6.4-1+b1
ii urlview 0.9-22
Versions of packages mutt is related to:
ii mutt 2.2.3-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Oh DRAT! I missed a lot of messages about this. I only just now got
your direct message to me. I was unaware of the bug ticket messages.
Very sorry.
[[ Normally I have a procmail recipe that automatically subscribes me
to any bug ticket with which I interact. Which means I don't normally
need to manually subscribe to bug. But that seems to have had a
failure of communication on this ticket and I was not subscribed to
it. Which means I missed the previous bug ticket only messages. :-( ]]
To answer a few of the previous questions regardless...
> Bob, what type of mailbox are you using (Maildir, mbox, IMAP...)
I use Maildir format on both a local XFS type file system and on
another system that NFS mounts the same. Both had the same behavior.
> What do your `mailboxes` lines in your muttrc look like? Do they have a
> trailing slash? If so, does the problem go away if you remove the
> trailing slash?
I have a mix. I probably have all of the possibilities.
mailboxes =Maildir/
mailboxes =listmail/
mailboxes =postmaster/
mailboxes =postmaster-spam/
mailboxes =Junk/
mailboxes `echo $HOME/Mail/Lists/gnu/*-announce`
mailboxes `echo $HOME/Mail/Lists/gnu/* | tr ' ' '\n' | grep -v -e /rt -e
audio-video`
unmailboxes $HOME/Mail/Lists/gnu/bug-gnulib
unmailboxes $HOME/Mail/Lists/gnu/emacs-devel
mailboxes `echo $HOME/Mail/Lists/nongnu/*`
mailboxes =stu-jokes
I think that is probably a representative sample. My actual list is
much longer. I am sure I have missed a few possible ways to (ab)use
the system but that covers most of the typical ones. :-)
> One change in 2.2.x was normalizing Maildir paths when opening them (as
> IMAP does) - removing a trailing delimiter. This might cause the
> behavior you are describing.
Oh! Thanks for looking at this!
Sorry I missed those messages. Then jumping to this last...
Kevin J. McCarthy wrote:
> Kevin J. McCarthy wrote:
> > Kevin J. McCarthy wrote:
> > > I don't know if you've compiled Mutt from git before, but if you are
> > > able and willing to try, I would appreciate hearing it that helped
> > > with your problem.
I could have easily compiled the git copy. I wish I had seen that
message in time for it to be relevant.
> > I've just released version 2.2.4 with a fix that I believe will also
> > address your issue.
> >
> > When you have a chance to test against 2.2.4, would you mind updating this
> > ticket to confirm/deny that is the case?
>
> Bob would you mind confirming that 2.2.4 fixes this issue for you?
I just unheld mutt on my Unstable Sid system. Upgraded to it. Tested
it. The problem I reported seems to be completely solved! I tested
this changing nothing but now using mutt 2.2.4 and all works as
before. I will close the bug with this message.
THANK YOU!
Bob
--- End Message ---
