Using: gnome-terminal-2.0.1-5 and vte-0.8.19-1 I can fairly reproducibly make gnome-terminal crash by doing: 1. start mutt in a gnome-terminal 2. change to a folder with many messages in, which takes 10+ seconds to load 3. resize the gnome-terminal window a few times whilst mutt continues to display its "Reading /home/jorton/mail/<folder> ... x y%" messages every 1000 messages. Here's the backtrace: (no debugging symbols found)... 0x420ae169 in wait4 () from /lib/i686/libc.so.6 #0 0x420ae169 in wait4 () from /lib/i686/libc.so.6 #1 0x4212a2d0 in __DTOR_END__ () from /lib/i686/libc.so.6 #2 0x408ecc63 in waitpid () from /lib/i686/libpthread.so.0 #3 0x40236ff5 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 #4 0x408ee47e in __pthread_sighandler () from /lib/i686/libpthread.so.0 #5 <signal handler called> #6 0x42028cc1 in kill () from /lib/i686/libc.so.6 #7 0x408eb07d in raise () from /lib/i686/libpthread.so.0 #8 0x4202a019 in abort () from /lib/i686/libc.so.6 #9 0x4093e476 in g_logv () from /usr/lib/libglib-2.0.so.0 #10 0x4093e4b4 in g_log () from /usr/lib/libglib-2.0.so.0 #11 0x400375fe in vte_terminal_ensure_cursor () from /usr/lib/libvte.so.2 #12 0x4003c325 in vte_terminal_insert_char () from /usr/lib/libvte.so.2 #13 0x4003d527 in vte_terminal_process_incoming () from /usr/lib/libvte.so.2 #14 0x40938c83 in g_idle_dispatch () from /usr/lib/libglib-2.0.so.0 #15 0x40935f65 in g_main_dispatch () from /usr/lib/libglib-2.0.so.0 #16 0x40936f98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #17 0x409372ad in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #18 0x40937a1f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #19 0x4043939f in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #20 0x08058256 in main () #21 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
This patch I think shows what is actually going on - cursor escaping off display top. Im not sure it is the right actual fix ultimately Alan
Created attachment 79985 [details] Stop vte dying, print message on bogus event
Hi Joe, Alan: Are either you two still seeing this behavior with a recent version of vte?
Ah this was fixed: http://bugzilla.gnome.org/show_bug.cgi?id=94509