Re: neomutt segmentation fault

On Thu, Oct 07, 2021 at 01:31:29PM +0100, Stuart Henderson wrote:
>On 2021/10/06 21:14, Jon Fineman wrote:
>> Not sure I built this correctly. I applied the patch, ran make in
>> ./mail/neomutt under my userid, then with doas after pkg_add issued errors.
>> I did not run make install.
>>
>> Is it valid to run neomutt out of the pobj directory? While it launched and
>> I was able to interact with it I did get the below errors about my config
>> file. The new neomutt is built without notmuch support, which I use.
>
>you can use FLAVOR=notmuch make [...]
>
>> > desktop(/usr/ports/pobj/neomutt-20211004/build-amd64)$: ./neomutt
>> > Error in /home/.config/neomutt/muttrc, line 9: nm_default_url: unknown
>> > variable
>> > Error in /home/.config/neomutt/muttrc, line 10: nm_query_type: unknown
>> > variable
>> > Error in /home/.config/neomutt/muttrc, line 11: Function
>> > 'vfolder-from-query' not available for menu 'index'
>> > Error in /home/.config/neomutt/muttrc, line 12: nm_db_limit: unknown
>> > variable
>> > Error in /home/.config/neomutt/maildir-muttrc, line 18:
>> > virtual-mailboxes: unknown command
>> > Error in /home/.config/neomutt/maildir-muttrc, line 24:
>> > virtual-mailboxes: unknown command
>> > Error in /home/.config/neomutt/maildir-muttrc, line 28:
>> > virtual-mailboxes: unknown command
>> > Error in /home/.config/neomutt/muttrc, line 190: source: file
>> > /home/.config/neomutt/maildir-muttrc could not be sourced
>> > source: errors in /home/.config/neomutt/muttrc
>> > Press any key to continue...
>
>those are all notmuch-related
>
>>
>> Also another dataum. I realized I often run neomutt and emacs/notmuch at the
>> same time. While I don't have a great recollection of the timing I am
>> starting to wonder if that is causing a conflict. The last day or so I have
>> not used emacs/notmuch and neomutt has been fine.
>>
>> Jon
>>
>>
>> On Tue, Oct 05, 2021 at 08:43:38AM +0100, Stuart Henderson wrote:
>> > On 2021/10/04 19:47, Stuart Henderson wrote:
>> > > On 2021/10/04 09:22, Jon Fineman wrote:
>> > > > I had been using it about 5 minutes and just entered a few commands.
>> > > > Hopefully one of these will help. dmesg follows. It is rather random with
>> > > > staying up days to just a few minutes.
>> > >
>> > > It probably needs reporting upstream, but there's a new release of
>> > > neomutt due this week so it would be better to test with that first, in
>> > > case the poblems you're running into have been fixed already.
>> > >
>> >
>> >
>> > Not the released version yet but you can try this:
>> >
>> > Index: Makefile
>> > ===================================================================
>> > RCS file: /cvs/ports/mail/neomutt/Makefile,v
>> > retrieving revision 1.66
>> > diff -u -p -r1.66 Makefile
>> > --- Makefile 5 Feb 2021 13:18:19 -0000 1.66
>> > +++ Makefile 5 Oct 2021 07:42:41 -0000
>> > @@ -4,7 +4,9 @@ COMMENT= tty-based e-mail client, Mutt w
>> >
>> > GH_ACCOUNT= neomutt
>> > GH_PROJECT= neomutt
>> > -GH_TAGNAME= 20210205
>> > +#GH_TAGNAME= 20210205
>> > +GH_COMMIT= a1660b20c3792075281d58ba1f902acfe1db0880
>> > +DISTNAME= neomutt-20211004
>> >
>> > CATEGORIES= mail
>> > HOMEPAGE= https://neomutt.org/
>> > Index: distinfo
>> > ===================================================================
>> > RCS file: /cvs/ports/mail/neomutt/distinfo,v
>> > retrieving revision 1.41
>> > diff -u -p -r1.41 distinfo
>> > --- distinfo 5 Feb 2021 13:18:19 -0000 1.41
>> > +++ distinfo 5 Oct 2021 07:42:41 -0000
>> > @@ -1,2 +1,2 @@
>> > -SHA256 (neomutt-20210205.tar.gz) = d+F3eA/C2Ku0ddnKxDQsfmHVPCQ/bOL5vIbYGfyWLNs=
>> > -SIZE (neomutt-20210205.tar.gz) = 3476980
>> > +SHA256 (neomutt-20211004-a1660b20.tar.gz) = Xl5IibCPVrlq30lx0L81C9YBQ+C++H6CgZcT7e/7Evk=
>> > +SIZE (neomutt-20211004-a1660b20.tar.gz) = 3726113
>> > Index: patches/patch-auto_def
>> > ===================================================================
>> > RCS file: /cvs/ports/mail/neomutt/patches/patch-auto_def,v
>> > retrieving revision 1.13
>> > diff -u -p -r1.13 patch-auto_def
>> > --- patches/patch-auto_def 5 Feb 2021 13:18:19 -0000 1.13
>> > +++ patches/patch-auto_def 5 Oct 2021 07:42:41 -0000
>> > @@ -3,7 +3,7 @@ $OpenBSD: patch-auto_def,v 1.13 2021/02/
>> > Index: auto.def
>> > --- auto.def.orig
>> > +++ auto.def
>> > -@@ -555,6 +555,7 @@ if {[get-define want-sasl]} {
>> > +@@ -579,6 +579,7 @@ if {[get-define want-sasl]} {
>> > define USE_SASL
>> > define-feature SASL
>> > } else {
>> > @@ -11,7 +11,7 @@ Index: auto.def
>> > foreach sasl_lib {sasl2 sasl} {
>> > if {[check-inc-and-lib sasl [opt-val with-sasl $prefix] \
>> > sasl/sasl.h sasl_encode64 $sasl_lib]} {
>> > -@@ -564,6 +565,7 @@ if {[get-define want-sasl]} {
>> > +@@ -588,6 +589,7 @@ if {[get-define want-sasl]} {
>> > break
>> > }
>> > }
>> > @@ -19,7 +19,7 @@ Index: auto.def
>> > if {![get-define USE_SASL]} {
>> > user-error "Unable to find SASL"
>> > }
>> > -@@ -1289,13 +1291,6 @@ set bare_rep {
>> > +@@ -1311,13 +1313,6 @@ set bare_rep {
>> > }
>> > set str_rep {
>> > PACKAGE_VERSION
>> > Index: patches/patch-nntp_newsrc_c
>> > ===================================================================
>> > RCS file: /cvs/ports/mail/neomutt/patches/patch-nntp_newsrc_c,v
>> > retrieving revision 1.5
>> > diff -u -p -r1.5 patch-nntp_newsrc_c
>> > --- patches/patch-nntp_newsrc_c 1 Sep 2020 10:50:55 -0000 1.5
>> > +++ patches/patch-nntp_newsrc_c 5 Oct 2021 07:42:41 -0000
>> > @@ -3,7 +3,7 @@ $OpenBSD: patch-nntp_newsrc_c,v 1.5 2020
>> > Index: nntp/newsrc.c
>> > --- nntp/newsrc.c.orig
>> > +++ nntp/newsrc.c
>> > -@@ -623,7 +623,7 @@ static int active_get_cache(struct NntpAccountData *ad
>> > +@@ -625,7 +625,7 @@ static int active_get_cache(struct NntpAccountData *ad
>> > if (!fp)
>> > return -1;
>> >
>> > Index: pkg/PLIST
>> > ===================================================================
>> > RCS file: /cvs/ports/mail/neomutt/pkg/PLIST,v
>> > retrieving revision 1.16
>> > diff -u -p -r1.16 PLIST
>> > --- pkg/PLIST 20 Nov 2020 17:17:21 -0000 1.16
>> > +++ pkg/PLIST 5 Oct 2021 07:42:41 -0000
>> > @@ -60,6 +60,9 @@ share/doc/neomutt/mime.types
>> > @sample ${SYSCONFDIR}/mime.types
>> > share/doc/neomutt/mimesupport.html
>> > share/doc/neomutt/miscellany.html
>> > +share/doc/neomutt/oauth2/
>> > +share/doc/neomutt/oauth2/mutt_oauth2.py
>> > +share/doc/neomutt/oauth2/mutt_oauth2.py.README
>> > share/doc/neomutt/optionalfeatures.html
>> > share/doc/neomutt/reference.html
>> > share/doc/neomutt/samples/
>> > @@ -110,11 +113,15 @@ share/locale/ko/LC_MESSAGES/neomutt.mo
>> > share/locale/lt/
>> > share/locale/lt/LC_MESSAGES/
>> > share/locale/lt/LC_MESSAGES/neomutt.mo
>> > +share/locale/nb_NO/
>> > +share/locale/nb_NO/LC_MESSAGES/
>> > +share/locale/nb_NO/LC_MESSAGES/neomutt.mo
>> > share/locale/nl/LC_MESSAGES/neomutt.mo
>> > share/locale/pl/LC_MESSAGES/neomutt.mo
>> > share/locale/pt_BR/LC_MESSAGES/neomutt.mo
>> > share/locale/ru/LC_MESSAGES/neomutt.mo
>> > share/locale/sk/LC_MESSAGES/neomutt.mo
>> > +share/locale/sr/LC_MESSAGES/neomutt.mo
>> > share/locale/sv/LC_MESSAGES/neomutt.mo
>> > share/locale/tr/LC_MESSAGES/neomutt.mo
>> > share/locale/uk/LC_MESSAGES/neomutt.mo
>>
>> --
>>

So far I have not had any crashes, which is good.

Although I am seeing two related minor annoyances (minor in that they
are easy to work around).

If I am viewing a message and new items come into the folder one of
two things can occur. The more common one is when I exit the message
by "q" the cursor will move to the first item. It used to stay on the
message you were on. The second less frequent one, depending on the
timing of quitting viewing a message and new items coming into the
folder, if you delete the message, then quit, the item that you were
viewing is not the item that gets deleted, but the first new item.