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 will SEGFAULT
> mutt.
[...]
> mutt 1.2.5i.
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
> mutt.
No it doesnt - mutt-1.2.5i
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.
> > ~/
> > hitting (twice) to get the directory listing
>
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?
On Thu, Apr 26, 2001 at 02:54:44PM -0700, CB <[EMAIL PROTECTED]> wrote:
> This is from a Mandrake mailing list. I wanted to point this out to th
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
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 following in my .muttrc, which
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]>
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
* steve [11-20-18 06:42]:
> 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]: segfa
steve hat am Di 20. Nov, 12:42 (+0100) geschrieben:
> 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.3
Le 20-11-2018, à 14:29:30 +0100, Jörg Sommer a écrit :
steve hat am Di 20. Nov, 12:42 (+0100) geschrieben:
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/kern
steve hat am Di 20. Nov, 15:18 (+0100) geschrieben:
> Le 20-11-2018, à 14:29:30 +0100, Jörg Sommer a écrit :
> > steve hat am Di 20. Nov, 12:42 (+0100) geschrieben:
> > > Hi There,
> > >
> > > I have a new box for about two months and it appears that each time mutt
> > > segfaults, the console fre
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
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 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
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
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
On Tue, Nov 20, 2018 at 12:42:02 +0100, steve wrote:
> 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:
When you say "the console freezes": are you able to lo
Hi,
Le 21-11-2018, à 17:51:39 -0500, Nathan Stratton Treadway a écrit :
On Tue, Nov 20, 2018 at 12:42:02 +0100, steve wrote:
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/
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
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
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
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 launc
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
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
On 20181122, Nathan Stratton Treadway wrote:
> 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
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 ^
Le 22-11-2018, à 07:35:08 -0800, Felix Finch a écrit :
On 20181122, Nathan Stratton Treadway wrote:
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
>
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
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 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.
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
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 =
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
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,
35 matches
Mail list logo
