GNOME Bugzilla – Bug 142111
Sudden Crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: gnome-terminal Severity: normal Version: GNOME2.6.1 2.6.1 Gnome-Distributor: Debian Synopsis: Sudden Crash Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.1) Description: Description of the crash: gnome-terminal crashes suddenly from time to time Steps to reproduce the crash: not known. How often does this happen? about once a day Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (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)...[Thread debugging using libthread_db enabled] [New Thread 1088535808 (LWP 21157)] (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)...0x40bec40e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 46727
Thread 1 (Thread 1088535808 (LWP 21157))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-05-07 10:23 ------- Unknown version 2.6.1 in product gnome-terminal. Setting version to "1.9.x". 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 meier@fnogol.de. 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.
What encoding are you using? This is most probably due to 139030, which has been fixed.
No response. 100% of stack of these stack traces were due to 139030, so I'll just use induction on this, and close this as a dup
*** This bug has been marked as a duplicate of 139030 ***