Hi There,
Just an update on this issue.
My machine just froze while NOT using mutt. I was in the terminal, typed
the few first letters of a command, then hit and the machine
froze. So to my big despair, it is not a mutt issue; I bet it's more a
hardware issue, and that is bad.
Have a nice day,
Le 23-11-2018, à 09:52:59 -0800, Kevin J. McCarthy a écrit :
On Fri, Nov 23, 2018 at 07:30:00AM +0100, steve wrote:
I think it's when I just go back from editing with vim to the pager.
Also, are you using IMAP?
Yes I do via offlineimap.
It sounds like this may be triggered by offlineimap
Le 23-11-2018, à 21:31:25 +0100, Jörg Sommer a écrit :
steve hat am Do 22. Nov, 16:19 (+0100) geschrieben:
Le 22-11-2018, à 16:09:50 +0100, Jörg Sommer a écrit :
> > #0 0x5592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024,
menu=, num=) at ../../curs_main.c:300
> > h =
steve hat am Do 22. Nov, 16:19 (+0100) geschrieben:
> Le 22-11-2018, à 16:09:50 +0100, Jörg Sommer a écrit :
>
> > > #0 0x5592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024,
> > > menu=, num=) at ../../curs_main.c:300
> > > h = 0x5592cbef1670
> > > flag = (MUTT_FOR
On Fri, Nov 23, 2018 at 07:30:00AM +0100, steve wrote:
I think it's when I just go back from editing with vim to the pager.
Also, are you using IMAP?
Yes I do via offlineimap.
It sounds like this may be triggered by offlineimap updating while you
are in the middle of composing the message.
Hi Kevin,
Le 22-11-2018, à 17:48:14 -0800, Kevin J. McCarthy a écrit :
On Thu, Nov 22, 2018 at 04:19:43PM +0100, steve wrote:
I would guess that one of the thread chains is broken. Does the
crash happen everytime in the same mailbox?
That's a question I also asked myself. I don't know for no
On Thu, Nov 22, 2018 at 04:19:43PM +0100, steve wrote:
I would guess that one of the thread chains is broken. Does the crash
happen everytime in the same mailbox?
That's a question I also asked myself. I don't know for now. I'll have
to investigate a bit more. The problem is that it doesn't ha
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 have seen screen (the command!) leave the tty in a very co
On 20181122, Felix Finch wrote:
> Try "stty sane^J".
I should have clarified; someimes the tty gets in such a state that it doesn't
echo any characters nor recognize ; you have to type this on blind faith
it's getting through to the shell, and the ^J works when doesn't. You
may need a ^C or ^
t'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 have seen screen (the command!) leave the tty in a very con
Le 22-11-2018, à 16:09:50 +0100, Jörg Sommer a écrit :
#0 0x5592c9a59c68 in index_make_entry (s=0x7fff20afb090 "", l=1024, menu=, num=) at ../../curs_main.c:300
h = 0x5592cbef1670
flag = (MUTT_FORMAT_TREE | MUTT_FORMAT_MAKEPRINT |
MUTT_FORMAT_ARROWCURSOR | MUTT_FORMAT_INDEX
steve hat am Do 22. Nov, 15:45 (+0100) geschrieben:
> Le 21-11-2018, à 23:10:51 +0100, Jörg Sommer a écrit :
>
> > > This does not tell me anything (I'm not a developer). Do you think I
> > > should
> > > open a bug report on the Debian BTS?
> >
> > Yes, this would be helpful. Do you have gdb in
s, 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 dou
Le 21-11-2018, à 23:10:51 +0100, Jörg Sommer a écrit :
This does not tell me anything (I'm not a developer). Do you think I should
open a bug report on the Debian BTS?
Yes, this would be helpful. Do you have gdb installed? Can you run
`coredumpctl debug` and run `bt full` on the gdb prompt? Th
ing to know if an instance of "htop" running on another
console continues keep running even after the segfault, for example.)
[...]
> No, nothing in syslog I think.
>
(It might be worth double-checking to make sure -- if for exam
Le 21-11-2018, à 23:10:51 +0100, Jörg Sommer a écrit :
steve hat am Mi 21. Nov, 19:50 (+0100) geschrieben:
# coredumpctl info
PID: 1678 (mutt)
UID: 1000 (steve)
GID: 1000 (steve)
Signal: 11 (SEGV)
Timestamp: Wed 2018-11-21 19:45:57 CET (17s ago)
Command
the
syslog file show any activity at all between the mutt segfault and the
restart-after-reboot messages?
No, nothing in syslog I think.
If a Mutt segfault is really able to lock up the system entirely, that
is a sign of a bigger problem with your kernel and/or hardware (i.e. a
user process such as M
t;: are you able to log in normally
using another virtual terminal or ssh session or anything? Or is the
system fully locked up, no longer responding to pings, etc.? Does the
syslog file show any activity at all between the mutt segfault and the
restart-after-reboot messages?
If a Mutt segfault is
steve hat am Mi 21. Nov, 19:50 (+0100) geschrieben:
> # coredumpctl info
> PID: 1678 (mutt)
> UID: 1000 (steve)
> GID: 1000 (steve)
>Signal: 11 (SEGV)
> Timestamp: Wed 2018-11-21 19:45:57 CET (17s ago)
> Command Line: mutt -y -n
>Executable: /usr/bin/m
Hi,
Mutt crashed just after hitting 'r'. Here is the output of
# coredumpctl info
PID: 1678 (mutt)
UID: 1000 (steve)
GID: 1000 (steve)
Signal: 11 (SEGV)
Timestamp: Wed 2018-11-21 19:45:57 CET (17s ago)
Command Line: mutt -y -n
Executable: /usr/bin/m
Le 21-11-2018, à 08:53:53 +0100, Jörg Sommer a écrit :
steve hat am Mi 21. Nov, 06:42 (+0100) geschrieben:
Le 20-11-2018, à 21:19:05 +0100, Jörg Sommer a écrit :
> > > Do you use systemd? Can you install the packages systemd-coredump and
> > > mutt-dbgsym? After a crash you can run `coredumpct
steve hat am Mi 21. Nov, 06:42 (+0100) geschrieben:
> Le 20-11-2018, à 21:19:05 +0100, Jörg Sommer a écrit :
>
> > > > Do you use systemd? Can you install the packages systemd-coredump and
> > > > mutt-dbgsym? After a crash you can run `coredumpctl info -1` and post
> > > > the
> > >
> > > There
Le 20-11-2018, à 21:19:05 +0100, Jörg Sommer a écrit :
> Do you use systemd? Can you install the packages systemd-coredump and
> mutt-dbgsym? After a crash you can run `coredumpctl info -1` and post the
There is no mutt-dbgsym in stretch, only jessie and sid. I installed
systemd-coredump. Will
me mutt
> > > segfaults, the console freezes and I have to hard stop the machine. Here
> > > is what I have in /var/log/kernel.log:
> > >
> > > Nov 19 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip
> > > 55a9d9996c68 sp 7
/kernel.log:
Nov 19 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip
55a9d9996c68 sp 7fff5e7f47c0 error 4 in mutt[55a9d9963000+115000]
Nov 19 15:54:17 box kernel: [ 7970.303284] Code: e1 00 01 41 89 cb 0f 84 c6 00
00 00 8b 4a 2c 03 8a 90 00 00 00 48 63 52 1c 39 d1 0f 8e cc 00
9 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip
> 55a9d9996c68 sp 7fff5e7f47c0 error 4 in mutt[55a9d9963000+115000]
> Nov 19 15:54:17 box kernel: [ 7970.303284] Code: e1 00 01 41 89 cb 0f 84 c6
> 00 00 00 8b 4a 2c 03 8a 90 00 00 00 48 63 52 1c 39 d1 0f 8e cc 00 00 00 45
70.303276] mutt[13832]: segfault at 8 ip
> 55a9d9996c68 sp 7fff5e7f47c0 error 4 in mutt[55a9d9963000+115000]
> Nov 19 15:54:17 box kernel: [ 7970.303284] Code: e1 00 01 41 89 cb 0f 84 c6
> 00 00 00 8b 4a 2c 03 8a 90 00 00 00 48 63 52 1c 39 d1 0f 8e cc 00 00 00 45 8b
> 54 92 fc 49 8b 5
Hi There,
I have a new box for about two months and it appears that each time mutt
segfaults, the console freezes and I have to hard stop the machine. Here
is what I have in /var/log/kernel.log:
Nov 19 15:54:17 box kernel: [ 7970.303276] mutt[13832]: segfault at 8 ip
55a9d9996c68 sp
Hello,
I have mutt with sidebar patch configured for two account in such a
way so it will change sidebar when changing the account. Unfortunately
I'm experiencing strange problems with display which are followed by
segfault. Its difficult to explain so I did a screen cast to
illustrate the
On Mon, Sep 6, 2010 at 3:42 PM, Asif Iqbal wrote:
> On Mon, Sep 6, 2010 at 3:01 PM, Asif Iqbal wrote:
>> When I run the following macro mutt exits with segfault
>>
>> macro index S
>> '/home/axisys/.mutt/script/reportspam.sh'
>>
>> Here is the
On Mon, Sep 6, 2010 at 3:01 PM, Asif Iqbal wrote:
> When I run the following macro mutt exits with segfault
>
> macro index S
> '/home/axisys/.mutt/script/reportspam.sh'
>
> Here is the script
>
> #!/bin/bash
> # take the email and send it as attachment
When I run the following macro mutt exits with segfault
macro index S
'/home/axisys/.mutt/script/reportspam.sh'
Here is the script
#!/bin/bash
# take the email and send it as attachment to abuse
# save to tmp file
spam=$(tempfile -s .eml)
abuse=ab...@example.net
cat > "$sp
On Fri, Mar 27, 2009 at 11:27:13PM +0100, Lagrange Marc wrote:
> Hi all,
>
> I've just compiled mutt 1.5.19 on my freebsd (7.1) laptop and mutt
> 1.5.19 is unable to start.
>
> I've a working config from another freebsd..
This sounds similar to the experience I have been having with the same
Fre
Hi all,
I've just compiled mutt 1.5.19 on my freebsd (7.1) laptop and mutt
1.5.19 is unable to start.
I've a working config from another freebsd..
All infos i can provides :
mutt -v
Mutt 1.5.19 (2009-01-05)
Copyright (C) 1996-2009 Michael R. Elkins and others.
Mutt comes with ABSOLUTE
I produced a segfault in Mutt 1.2.5i as follows.
I have a folder hook set for mbox to show only new messages. I started
Mutt, went to mbox. Deleted the one message which was marked as new. I
then pressed $ to update mbox, thinking this would show the remaining
contents (which is over 300
begin Bob Bell quotation:
> I'm unable to reproduce this with mutt 1.3.11i. Have you tried to
> reproduce it? Do you have a few short lines I can add to my muttrc to
> reproduce it?
No, I was not able to reproduce it, sorry I forgot to mention that. I
took it for granted that he was giving me
nt this out to the
> developers and let them know that an audit might be in order to
> verify/disprove that this exists in other config options as well (the
> segfault on a blank option).
>
> >Forwarded message
> I just wanted to update the group on this issue.
>
This is from a Mandrake mailing list. I wanted to point this out to the
developers and let them know that an audit might be in order to
verify/disprove that this exists in other config options as well (the
segfault on a blank option).
>Forwarded message
I just wanted to update
Look at your "set editor" function.
On Sat, Mar 03, 2001 at 12:14:29AM +0100, Marco Ahrendt muttered:
| hi all,
|
| anyone knows why mutt crashes with segmentation fault if i press "y" to
| send the message ?? i'm running kernel 2.4.1 and mutt 1.3.12i.
|
| Marco
|
| --
| Marco Ahrendt
hi all,
anyone knows why mutt crashes with segmentation fault if i press "y" to
send the message ?? i'm running kernel 2.4.1 and mutt 1.3.12i.
Marco
--
Marco Ahrendt phone : +49-341-98-474-0
adconsys AGfax : +49-341-98-474-59
Karl-Liebknecht-Str. 19email
Hi, Thomas.
Just an update on occurrences of segfault. I've changed my .muttrc setting around a
bit to change
the way a folder is displayed when first opened. I have the following:
folder-hook =mbox 'push odl~N'
folder-hook =outbox 'push od
folder-hook =CGO_Chorus &
On Fri, Dec 01, 2000 at 04:05:14PM +0530, Suresh Ramasubramanian wrote:
> Johannes Zellner proclaimed on mutt-users that:
>
> > I discovered a reproducable SEGFAULT:
> > using c to change folder
> > c
> > using a directory, e.g.
> > ~/
> > hit
Johannes Zellner proclaimed on mutt-users that:
> I discovered a reproducable SEGFAULT:
> using c to change folder
> c
> using a directory, e.g.
> ~/
> hitting (twice) to get the directory listing
> and then using `m' to compose a mail will SEGFAULT
>
Hello Johannes,
* Johannes Zellner wrote:
> I discovered a reproducable SEGFAULT:
>
> using c to change folder
>
> c
>
> using a directory, e.g.
>
> ~/
>
> hitting (twice) to get the directory listing
> and then using `m' to compose a mail
Hi,
I discovered a reproducable SEGFAULT:
using c to change folder
c
using a directory, e.g.
~/
hitting (twice) to get the directory listing
and then using `m' to compose a mail will SEGFAULT
mutt.
So the key stokes again:
c~/m
I'm not subscribed to the list, so
On 2000-11-01 21:53:46 -0500, John P. Verel wrote:
> I've just determined that this is confined to one particular folder.
Could you please try to confine this further, possible to one
particular thread in that folder?
--
Thomas Roessler <[EMAIL PROTECTED]>
I've just determined that this is confined to one particular folder.
On 11/01/00, 09:15:47PM -0500, John P. Verel wrote:
> I can always produce a segfault with the following sequence, while in
> in a folder:
>
> order|date|End|Order|Thread|Up Arrow
>
> I have the followi
I can always produce a segfault with the following sequence, while in
in a folder:
order|date|End|Order|Thread|Up Arrow
I have the following in my .muttrc, which may be germane:
folder-hook . 'push V'
I'm running Red Hat 7, 2.2.16-22.
I do not recall this happening in 1.
On Sat, Sep 16, 2000 at 19:02:32 +0200, Zak Le Roux wrote:
> Forgot to add the CORE DUMP file (gzipped) ... sorry !
We cannot use the core file without having exactly the same
environment and the executable file as where it was made.
You can however help by analyzing the core with the gdb
Forgot to add the CORE DUMP file (gzipped) ... sorry !
Hi,
I have recently installed the new version of Mutt (1.2.5i). I am new to
this application and find it tough going. but I am learning a lot. I am
however having some trouble with it ... causes a segmentation fault and
core dumps when I ex
Hi,
I have recently installed the new version of Mutt (1.2.5i). I am new to
this application and find it tough going. but I am learning a lot. I am
however having some trouble with it ... causes a segmentation fault and
core dumps when I exit from sometimes. Here are some details that may be
help
The attached patch fixes a segmentation fault which would occur when
the operates without a Context (this happens, for instance, when you
can't connect to an IMAP folder).
--
http://www.guug.de/~roessler/
Index: imap/util.c
===
RC
i recently downloaded /mutt-0.96.2/ and still get the annoying segfault
when syncing the mailbox...
(gdb) bt
#0 0x400b4ef1 in _IO_old_file_close_it (fp=0x80c90f0) at oldfileops.c:140
#1 0x400b1257 in freopen (filename=0x80c9050 "/var/spool/mail/martin", mode=0x80a4821
"r+&quo
53 matches
Mail list logo
