GNOME Bugzilla – Bug 394996
crash in Terminal: I pressed the close butt...
Last modified: 2007-03-17 20:19:06 UTC
Version: 2.16.1 What were you doing when the application crashed? I pressed the close button of a tab inside the terminal Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 75841536 vsize: 0 resident: 75841536 share: 0 rss: 16891904 rss_rlim: 0 CPU usage: start_time: 1168426990 rtime: 0 utime: 264 stime: 0 cutime:230 cstime: 0 timeout: 34 it_real_value: 0 frequency: 292 Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226008912 (LWP 6213)] [New Thread -1268061280 (LWP 6219)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 100967
Thread 1 (Thread -1226008912 (LWP 6213))
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!
Hello Tom, In order to give you the backtrace I will have to let the terminal crash again. The problem is that this rarely happends to me. However, I can describe what happened. Beryl was enabled and the terminal went unresponding, I thought that the application within the terminal (I started some application using the terminal) was hogging up resources and rapidly clicked the close button of the tab. Sorry that I cannot be more exact by giving backtraces.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 353498 ***