GNOME Bugzilla – Bug 109624
gnome-terminal crashes after closing window.
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-terminal Severity: normal Version: 2.2.1 Synopsis: gnome-terminal crashes after closing window. Bugzilla-Product: gnome-terminal Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Gnome-terminal crashes after closing a window after a command has been run. Steps to reproduce the problem: 1. Open multiple gnome-terminals 2. Run a command: top, xterm, galeon, etc. 3. After command has finished, logout with Ctrl-D. 4. Fatal error is reported and all gnome-terminal windows close. Actual Results: Fatal error resulting in all windows being closed. Expected Results: No fatal error. How often does this happen? Everytime. Additional Information: I reported this earlier when I experienced this with my laptop running Debian unstable. However, after I submitted the bug report, I cannot reproduce the problem on my laptop. I still experience the problem on my Desktop machine, so I'm going through the same steps I did with my laptop to see if it stops (I have no idea why submitting a bug report would help anything...). So this can be considered a duplicate bug of the one I filed earlier... 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 25451)] (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)...0x40b66b89 in wait4 () from /lib/libc.so.6
+ Trace 35418
Thread 1 (Thread 16384 (LWP 25451))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-31 11:19 ------- The original reporter (jdhutchison11@attbi.com) 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.
It turns out that this is only happening when the user's account is hosted on an NFS server. Local accounts only experience the problem once (eg. like my laptop), but after that, I can't get gnome-terminal to crash. However, the NFS accounts are really consistent. Everytime I open a couple windows, run any command in a window, and then close the window, gnome-terminal crashes. I have verified the local vs. NFS behaviour on my desktop and laptop using 3 different user accounts. I captured the error message that gnome-terminal was displaying when it crashed: ** ERROR **: file vte.c: line 7013 (vte_terminal_process_incoming): assertion failed: (_vte_buffer_length(terminal->pvt->incoming) > 0) aborting...
*** Bug 109609 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 107234 ***