-   Slackware (
-   -   Mutt Segfaults in 14.0 (

HaroldWho 02-07-2013 08:16 AM

Mutt Segfaults in 14.0
New install of 14.0 with mutt-1.5.21-i486-2; mutt segfaults. Recompiled from Slack source with SlackBuild, no joy.

Anyone else seen this? Ideas? Fix?

business_kid 02-07-2013 10:47 AM


ldd /path/to/mutt |grep found
Whatever that mentions is missing. It's i486. Have you a 32 bit cpu, or a multilib 64 bit system?

HaroldWho 02-08-2013 02:33 PM

That was a good idea; I'm embarrassed not to have thought of it. Alas, no libs are missing. BTW, it's a 32-bit Intel Core 2 Duo E6300 with Intel D975XBX2KR board. For now I'm happily using an older version of mutt; not sure what the new version in 14.0 actually buys me.

business_kid 02-08-2013 02:39 PM

Maybe a few more/less fleas? :-). From 'man mutt'

      None.  Mutts have fleas, not bugs.

      Suspend/resume  while  editing  a file with an external editor does not
      work under SunOS 4.x if you use the curses lib in /usr/5lib.  It  does
      work with the S-Lang library, however.
      Suspend/resume does not work under Ultrix.

      The help line for the index menu is not updated if you change the bind-
      ings for one of the functions listed while Mutt is running.

      For  a more up-to-date list of bugs, errm, fleas, please visit the mutt
      project's bug tracking system under

san 02-08-2013 04:53 PM

did it work with 13.37? this might just be mutt's reaction to an option in the .muttrc that is not compiled in. you could compare `mutt -v` to your config file.

Poucket 02-08-2013 05:30 PM

Hello HaroldWho,

Sometimes when I have misconfigured my muttrc, mutt does not start at all.
Have you been able to reproduce the segfaults?

On 1.5.21-x86_64 mutt has behaved well, although a while ago I had
a problem with mutt freezing. It seemed to happen randomly, or at times when
I was doing something fancy such as reading a message while logged into a
remote mail server, then following a url in the message, then closing the
browser and resuming my session with mutt. These were not segfaults, however.
Mutt would not exit and dump its memory. I would have to chvt to restart.

HaroldWho 02-11-2013 03:08 PM

I haven't used mutt-1.5.21 before. as I had Slack 13.1. As for the .muttrc config file, mutt only complains about the "alternates" variable. Still segfaults without any further messages if the "alternates" var is commented out.

I d/l'd the source from and configured it w/o POP, NLS, or IMAP. Compiles but still segfaults. I'm gonna try recompiling with S-lang instead of ncurses.

Since I have a working version of mutt I'm not going down this road too far though.

TobiSGD 02-11-2013 03:48 PM

Using Mutt on 14.0 32 Bit and 64 Bit (64 Bit now updated to -current) without any problems.

Poucket 02-11-2013 06:24 PM


Originally Posted by TobiSGD (Post 4889406)
Using Mutt on 14.0 32 Bit and 64 Bit (64 Bit now updated to -current) without any problems.

Nor any problems here.


Still segfaults without any further messages if the "alternates" var is commented out.
HaroldWho, in the last few days I have changed muttrc and have managed to produce some segfaults.
What I do not understand is why you must recompile. For me, segfault ends when I
revert whatever change I've made that produces a segfault.

HaroldWho 02-12-2013 02:54 PM

From what I've seen here so far I need to pay closer attention to my ~/.muttrc file. BTW, mutt seems to ignore the -F field to specify another config file. Only seems to look for ~/.muttrc or /etc/mutt/Muttrc.

I recompiled because I don't need POP, NLS, or IMAP in Mutt. BTW, segfaults whether compiled against ncurses or S-lang.

Here's what the syslog shows after a segfault Means nothing to me:


Hound kernel: [ 3041.107246] mutt[3506]: segfault at 0 ip 08074f4f sp bfa08ea0 error 4 in mutt[8048000+c6000]
I still have a few ideas to try; then it stick with

Thanks for all the ideas.

Poucket 02-12-2013 06:27 PM


Originally Posted by HaroldWho (Post 4890173)
BTW, mutt seems to ignore the -F field to specify another config file. Only seems to look for ~/.muttrc or /etc/mutt/Muttrc.

Just tried that option, and mutt did not ignore it. After mutt started it was configured exactly as specified.

Thanks for keeping us posted.


I don't need POP, NLS, or IMAP
What does the +nls add?

HaroldWho 02-13-2013 03:47 PM

OK, the segfault problem is due to some unrecognized/screwed-up variable in my old ~/.muttrc file. Mutt complains about the "alternates" variable, but something is still there that just causes a segfault. I built a quick-and-dirty Muttrc using (a very interesting site BTW) and no segfault. Downside: appearance not at all what I want, and I doubt I'll spend the time on a new Muttrc when mu old Mutt works fine.

BTW, all NLS gives you is support for a lot of non-English languages.

Again, thank you all for the ideas and suggestions.

Poucket 02-13-2013 07:18 PM

Nice site. The muttrcbuilder is very interesting.
(edit link?)

Muttrc does do more than set variables. For example, read the mutt documentation about Alternative Addresses.
Confusingly, "alternates" isn't a variable.

You can also read the same documentation when using mutt by pressing F1 -if that key is not already mapped.

All times are GMT -5. The time now is 03:31 AM.