Le 22-11-2018, à 02:09:46 -0500, Nathan Stratton Treadway a écrit :
On Thu, Nov 22, 2018 at 07:51:48 +0100, steve wrote:
No. If switch to another console, and launch a 'ls' for example, the
cursor goes to the line and then nothing happens. Ctlr-x doesn't do
anything. Opening a new one and launching htop for example freeze the
terminal. But was it funny, is that I can firefox still works as
expected. At this stage I normally shutdown the computer physically.
Hmmm, interesting... the system is not truely locked up, but perhaps
it's now unable to launch new processes, or something like that. (It
would be interesting to know if an instance of "htop" running on another
console continues keep running even after the segfault, for example.)
I'll leave an htop running just in case.
[...]
No, nothing in syslog I think.
(It might be worth double-checking to make sure -- if for example [Byour
follow-on attempts to run "ls" and "htop" also show up as segfaults in
the log, that would certainly tell you something.)
Double checked and I'm pretty sure there is nothing else.
Yes, I think it might be a hardware problem triggered by a mutt
segfault. Still looking around.
(The distinction may not matter in the end, but off hand I'd suspect the
hardware fault [or whatever it is] is causing both the mutt segfault and
the other symptoms you are seeing.)
It's really only mutt (or neomutt…) that triggers the problem, no other
program.
Anyway, good luck tracking it down...
Thank you, I hope I can succeed (with your and Jörg nice help).
Best,
Steve
