GNOME Bugzilla – Bug 109784
exiting one shell crashes *all* terminals
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-terminal Severity: normal Version: 2.2.1 Synopsis: exiting one shell crashes *all* terminals Bugzilla-Product: gnome-terminal Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: I had 9 gnome-terminal instances running, and decided to close one of them by exiting the shell. All the running terminals then crashed. Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? Twice in two days. It's not 100% repeatable. A quick glance through the debian bug list for gnome-terminal suggests others may be seeing this and it may be related to fonts. I recently had to change fonts (to courier). The gnome-terminal binary has not changed in two months. Additional Information: Here's the tail end of .gnome-errors. The first message was repeated 10 times. ** (gnome-terminal:12094): WARNING **: No handler for control sequence `device-control-string' defined. ** ERROR **: file vte.c: line 7013 (vte_terminal_process_incoming): assertion failed: (_vte_buffer_length(terminal->pvt->incoming) > 0) aborting... Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 12094)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40b6ab89 in wait4 () from /lib/libc.so.6
+ Trace 35488
Thread 1 (Thread 16384 (LWP 12094))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-02 08:51 ------- The original reporter (steven.robbins+gnome@videotron.ca) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, hp@redhat.com.
*** This bug has been marked as a duplicate of 107234 ***