GNOME Bugzilla – Bug 131868
Gnome terminal crash
Last modified: 2009-08-15 18:40:50 UTC
Distribution: Debian testing/unstable Package: gnome-terminal Severity: normal Version: GNOME2.4.1 2.4.2 Gnome-Distributor: Debian Synopsis: Gnome terminal crash Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.4.2 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: When use an application in a server via SSH protocol, the terminal crash Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: 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)...[New Thread 16384 (LWP 6212)] (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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x404bbbb8 in waitpid () from /lib/libpthread.so.0
+ Trace 43323
Thread 1 (Thread 16384 (LWP 6212))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-01-18 18:22 ------- Unknown version 2.4.2 in product gnome-terminal. Setting version to the default, "unspecified". The original reporter (paulino@michelazzo.com.br) 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, gnome-terminal-maint@bugzilla.gnome.org.
Thanks for the bug report. The stack trace appears to be unique from the simple-dup-finder, but it doesn't look very useful. Is there any chance you could get us another one? See http://bugzilla.gnome.org/getting-traces.cgi for more information about obtaining a useful stack trace.
No response from the reporter. Closing. Reporter: if you can still reproduce this and are able to provide a stack trace with debugging symbols, please reopen.