neomutt segmentation faults when command line email sent

Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

neomutt segmentation faults when command line email sent

myportslist20190323
Synopsis: neomutt segmentation faults when command line email sent

Category:       user
Environment:    OpenBSD 6.6 Details     : OpenBSD 6.6-current
  (GENERIC.MP) #427: Sat Nov  2 13:23:11 MDT 2019
  [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP

    Architecture: OpenBSD.amd64 Machine     : amd64
Description:
    Neomutt segmentation faults when command line email is sent.
How-To-Repeat:
    echo "hi there" | neomutt -s hi root@localhost
    OR
    neomutt -s somesubject [hidden email] < sometextfile

    This happens with or without a subject, to any email address. It
    also happens with or without a muttrc or neomuttrc file present.

    It happens on several different current boxes with different
    hardware, including one box with kern.version=OpenBSD 6.6-current
   (GENERIC) #410: Tue Nov  5 17:00:09 MST 2019
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC,
    and no packages other than neomutt dependencies.

    Sending email with neomutt from the command line stopped working
    for me around Oct 27. I use cwm and have tried from an xterm
    with and without tmux.

    Sending does with neomutt-20180716p1-gpgme-sasl on one box that
    runs 6-6.current GENERIC.MP #389.

    I've tried neomutt-20191102-gpgme-sasl and neomutt-20191102 on a
    few current boxes, but it always seg faults.

    I'm very sorry that I don't know where to start fixing it. I
    will also build it from ports on another current box. I can
    include a diff of neomutt -D  5 on a working vs nonworking
    version if needed. I could run gdb on neomutt, but I'm not sure
    how to run it on something like "neomutt [hidden email]
    </tmp/abcdefg."

    Looking at the source code like a monkey at a monolith, I see in
    main.c that the address of bodytext is passed to
    mutt_parse_mailto, but I don't understand where bodytext gets
    the actual text of the body. It must be there, I just don't
    understand. I mention it on the off chance that that might
    help.

    As a separate issue, I notice the N showing which mailboxes
    have new mail seems to have disappeared. If I set the sidebar
    as suggested in the neomutt guide with sidebar_format =
    "%B%?F? [%F]?%* %?N?%N/?%S" it will show which boxes
    have new mail, but the N next to the mailbox doesn't appear.
    That happens with or without the sidebar visible. It used
    to work in the previous version. Of courses, that's with a
    .neomuttrc with mailboxes defined.
 
    Even with these bugs, neomutt is still great and lets me escape
    webmail and other slow email clients.

    I would like to thank all the developers. OpenBSD is amazing.
    I run my business using only OpenBSD machines -- routers,
    access points, webservers, and yes all my desktop machines.
    Thank you!

    (I don't think this will be on the ports list, but  I apologize
    if that happens. I accidentally sent to ports before subscribing.)

Reply | Threaded
Open this post in threaded view
|

Re: neomutt segmentation faults when command line email sent

Stuart Henderson
On 2019/11/06 09:55, [hidden email] wrote:
> Synopsis: neomutt segmentation faults when command line email sent

neomutt recently had an update with over a year's refactoring work and
as mentioned in the commit log :

: update to neomutt-20191025, as upstream say this has a lot of changes
: but should be ok for general use.
:
: see https://github.com/neomutt/neomutt/releases/tag/2019-10-25 for more
: information and help request.

This particular bug was fixed upstream a couple of days ago,
https://github.com/neomutt/neomutt/issues/1943

I'll backport that commit now, but I would expect another upstream release
including it fairly soon anyway.

>     (I don't think this will be on the ports list, but  I apologize
>     if that happens. I accidentally sent to ports before subscribing.)

Generally unless a problem seems specific to OpenBSD it's best to report
bugs upstream. Maybe cc or send the ticket URL to the port maintainer
("pkg_info neomutt" will show you this) or to ports@. This ports-bugs@
list is pretty much unused and you're lucky I saw it here!.