GNOME Bugzilla – Bug 165142
Gnome-terminal random crash
Last modified: 2005-01-25 00:17:17 UTC
Distribution: Debian 3.1 Package: gnome-terminal Severity: normal Version: GNOME2.8.1 2.8.0 Gnome-Distributor: Debian Synopsis: Gnome-terminal random crash Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.8.0 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: I clicked gnome terminal open from taskbar (it was minimized) and after that it crashed suddenly Steps to reproduce the crash: 1. - 2. - 3. - Expected Results: I tried to re-produce the crash but i couldnt do it. How often does this happen? This happens randomly and it losts all the saved profiles along the crash. Additional Information: 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 1088716608 (LWP 11653)] [New Thread 1104145328 (LWP 11661)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x40c48511 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 54884
Thread 1 (Thread 1088716608 (LWP 11653))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-24 18:37 ------- Unknown version 2.8.0 in product gnome-terminal. Setting version to "2.8.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' 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.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system; it would be helpful if you could answer the question(s) in bug 157945. *** This bug has been marked as a duplicate of 157945 ***