mutt problems after upgrading glibc

[Gregory Nowak]

Hi all.

I guess I have a hat full of problems tonight. After installing all the x stuff that comes with slack 9.1, I also had to upgrade glibc to the one that comes with slack 9.1, since x was complaining about that.

After upgrading glibc, I found that I am having problems using mutt. Specifically, I can read and delete messages just fine. However, whenever I try to either start a new message, or reply to a message, I get asked either for "subject", or "include message in reply", depending on the situation. When I hit enter here, mutt gets a segmentation fault, and I imagine the same would probably happen when forwarding a message. I upgraded to the mutt package with slackware 9.1, but that doesn't help. In fact, it seems to me that the mutt packages for slack 9.0 and 9.1 are the same one. 

I tried using gdb, but was told there were no debugging symbols found. Since I imagine that others are using mutt just fine with slackware 9.1, there has to be a problem in my setup. All I upgraded is the x/gnome stuff, glibc, and mutt. I left everything else alone, since it seems to be working fine so far. Can someone please give me a clue as to what to check for, or what other packages to upgrade?

I should mention here that my editor is not the problem. I have my VISUAL and EDITOR variables exported to use emacs, which runs just fine on its own. When I comment out the lines in my .profile which export VISUAL and EDITOR, and I log out and back in, mutt still gets a segmentation fault. Yes, vi runs on its own just fine as well.

I know someone might suggest that I upgrade the entire system, but I'm not prepared to do that just now. Someone will probably also ask how I am writing this email, if I can't write email. The answer to that one is that I'm doing it from another box (smile).

Any input would be greatly appreciated.
Thanks in advance.

Greg


-- 
Free domains: http://www.eu.org/ or mail dns-manager at EU.org