crash: sort-mailbox/sort-reverse in message-attach mode

[nabijaczleweli]

sort-mailbox/sort-reverse doesn't work when switching to same type but different reversing in message-attaching mode (A); explodes when switched to different type?

Expected Behaviour

It sorts normally.

Actual Behaviour

First it didn't work (I'm usually on last-date-received/reverse-threads, I was trying to switch to t for forward-threads to order the attached messages better. This changed nothing. Then I did d for date and it exploded.

Unfortunately, this is a work-ish mailbox so I cannot post the screenshot here directly (sorry!), but here's the screenshot, encrypted for @flatcap's personal: sort-moment.png.gpg.gz

Steps to Reproduce

Start off with

set sort = 'reverse-threads'
set sort_browser = 'reverse-date'
set sort_aux = 'last-date-received'

make a mail, A to the mailbox below, ot, observe nothing happens, od observe it explodes.

This persists across q/A cycles.

How often does this happen?

• On a particular mailbox: sort-moment.mbox.gpg.gz (again, encrypted as above, I trust your privacy on this)

When did it start to happen?

No clue

NeoMutt Version

NeoMutt 20220429
Copyright (C) 1996-2022 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type 'neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type 'neomutt -vv' for details.

System: Linux 5.10.0-14-amd64 (x86_64)
ncurses: ncurses 6.2.20201114 (compiled with 6.2.20201114)
libidn: 1.33 (compiled with 1.33)
GPGME: 1.14.0-unknown
GnuTLS: 3.7.1
libnotmuch: 5.3.0
storage: lmdb
compression: zlib, zstd

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} {--libexecdir=${prefix}/lib/x86_64-linux-gnu} --disable-maintainer-mode --disable-dependency-tracking --mandir=/usr/share/man --libexecdir=/usr/libexec --with-mailpath=/var/mail --gpgme --lua --notmuch --gnutls --gss --idn --mixmaster --sasl --lmdb --zlib --zstd --testing

Compilation CFLAGS: -g -O2 -ffile-prefix-map=/home/nabijaczleweli/backports/build-output/neomutt-20220429+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -std=c99 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D__EXTENSIONS__ -I/usr/include -I/usr/include/lua5.4 -DNCURSES_WIDECHAR -isystem /usr/include/mit-krb5

Default options:
  +attach_headers_color +compose_to_sender +compress +cond_date +debug
  +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color
  +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop
  +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar
  +skip_quoted +smtp +status_color +timeout +tls_sni +trash

Compile options:
  -autocrypt +fcntl -flock -fmemopen +futimens +getaddrinfo +gnutls +gpgme +gss
  +hcache -homespool +idn +inotify -locales_hack +lua +mixmaster +nls +notmuch
  -openssl +pgp +regex +sasl +smime -sqlite +sun_attachment

MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: https://neomutt.org
If you find a bug in NeoMutt, please raise an issue at:
    https://github.com/neomutt/neomutt/issues
or send an email to: <[email protected]>

Extra Info

• Operating System and its version: bullseye
• Were you using multiple copies of NeoMutt at once? no
• Were you using 'screen' or 'tmux'? no
• Is your email local (maildir) or remote (IMAP)? IMAP

[nabijaczleweli]

After sending the mail, the actual sorting order in normal index view was unaffected? This is how it looks normally: after.png.gpg.gz

[flatcap]

Thanks for the bug report and data. I can imagine what's going wrong, but I can't repeat it. I'll keep thinking. Meanwhile, if you can reproduce the crash and get a backtrace, that'd really help. Thanks

[nabijaczleweli]

It doesn't crash though?

[flatcap]

I couldn't get it to crash. I thrashed it with loads of sorting changes, but nothing.

[nabijaczleweli]

If by crash you mean like a segfault, then I couldn't either. If by crash you mean that it does the weird thing, then I can repro this once more, but only if I tag some mails? I got to this state with (starting in the mailbox i attached, dunno if it'd happen in any others): m{whatever to get to the message editor}A<Enter><Esc>todot

[flatcap]

Ah, ok. I saw some ugly threading arrows, but your original title said: EXPLODES -- I assumed that meant a crash