GNOME Bugzilla – Bug 397660
crash in Terminal: Trying to get in the sus...
Last modified: 2007-07-15 10:13:14 UTC
Version: 2.16.0 What were you doing when the application crashed? Trying to get in the suspended mode, when I woke the computer the crash message appeared Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 102395904 vsize: 0 resident: 102395904 share: 0 rss: 10899456 rss_rlim: 0 CPU usage: start_time: 1168986965 rtime: 0 utime: 2202 stime: 0 cutime:1784 cstime: 0 timeout: 418 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208142128 (LWP 2329)] [New Thread -1213711472 (LWP 2334)] (no debugging symbols found) 0x0049a402 in __kernel_vsyscall ()
+ Trace 102989
Thread 1 (Thread -1208142128 (LWP 2329))
Unique trace Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 408497 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!