SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
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 http://bugs.mutt.org/.
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.
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 mutt.org 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.
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.
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: 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 220.127.116.11i
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 http://muttrcbuilder.org/page (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.