I can still reproduce this bug with Ubuntu-9.10 Karmic (tested in a xterm). It happens rarely but I managed to reproduce it at least twice.
I happens more often if I run it strace.
I ran...
$ strace -s 3000 -f -o /tmp/trace-xterm xterm
And in the xterm, I ran the non existing command:
$ foobar&
xterm exited immediately! (but it does not happen all the time when I try again).
In the log file /tmp/trace-xterm, I see something interesting shortly before it exits:
334 write(2, "Sorry, command-not-found has crashed! Please file a bug report at:", 66) = -1 EIO (Input/output error)
I attach the full /tmp/trace-xterm log file.
I can still reproduce this bug with Ubuntu-9.10 Karmic (tested in a xterm).
It happens rarely but I managed to reproduce it at least twice.
I happens more often if I run it strace.
I ran...
$ strace -s 3000 -f -o /tmp/trace-xterm xterm
And in the xterm, I ran the non existing command:
$ foobar&
xterm exited immediately! (but it does not happen all the time when I try again).
In the log file /tmp/trace-xterm, I see something interesting shortly before it exits:
334 write(2, "Sorry, command-not-found has crashed! Please file a bug report at:", 66) = -1 EIO (Input/output error)
I attach the full /tmp/trace-xterm log file.