GNOME Bugzilla – Bug 138866
gnome-terminal randomly hangs.. this time it finally crashed
Last modified: 2005-04-17 19:08:46 UTC
Package: gnome-terminal Severity: normal Version: 2.2.1 Synopsis: gnome-terminal randomly hangs.. this time it finally crashed Bugzilla-Product: gnome-terminal Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: My gnome-terminal seems to hang randomly for periods at a time. I tend to have ssh sessions going to remote machines and one is a screen session. The screen session tends to need a fair bit of repainting requests. Anyway, this time I decided to bring it up in gdb when it hung, it looked like vte was stuck in some sort of loop. Usually after a few minutes gnome-terminal wakes up again and lets me continue to use it. Sorry if this bug report is useless.... 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)...[New Thread 1087386912 (LWP 6407)] 0xffffe002 in ?? ()
+ Trace 45625
Thread 1 (Thread 1087386912 (LWP 6407))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-02 12:03 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was gnomebug@tainted.org. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
(This stack looks broken...) Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces. I'll move this to vte in the meantime...
If there are any known crash issues with using screen in a tab, then this is likely part of those family of bugs. The problems have gotten severe enough that I've started using konsole.
The thing is, this is a weird error in that the stack trace you provided is impossible. _But_ it has already been reported, which means something is amiss somewhere: the stack trace in bug 106487 is exactly like this one. The reporter of that bug did not follow up on Nalin's questions, so it never got really looked into. If you could answer the questions and provide a stack trace with symbols etc it would be very helpful.
*** Bug 140057 has been marked as a duplicate of this bug. ***
Bug 140057 has some specific steps to reproduce (I can't, tho) and details of the system.
*** Bug 140009 has been marked as a duplicate of this bug. ***
Same comment on 140009. Something wrong with the debian/testing build? ALl these stack traces have the impossible call to vte_terminal_set_default_colors from vte_terminal_fork_command.
*** Bug 140289 has been marked as a duplicate of this bug. ***
I'd also like to add that one of my tabs is running a screen session. The session is to a Debian box (ie would be using a Debian termcap). I just upgraded my laptop to Fedora Core 2 and gnome-terminal seems to still hang.
This bug appears to be identical to the bug I filed over a year ago. Please see bug 117945, it is identical. I'm even on a completely different machine now, SuSE 9.1 which gnome updates, and here is another backtrace (provided while the gnome-terminal was "hung", I cracked open gdb and attached to the process in an xterm):
+ Trace 49934
Can somebody mark this as a duplicate of 117945 (or whatever appropriate merging activity there is).
*** This bug has been marked as a duplicate of 117945 ***
*** Bug 141355 has been marked as a duplicate of this bug. ***