GNOME Bugzilla – Bug 409578
crash in Terminal: It was backgrounded, the...
Last modified: 2007-02-19 14:51:34 UTC
Version: 2.16.1 What were you doing when the application crashed? It was backgrounded, there was an SSH connection in the terminal ... nothing special, really. A few minutes ago Beryl crashed and ran Metacity as it's fall-back window manager ... maybe that's related. I didn't temper with it; i've continued to use Metacity since then. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 79958016 vsize: 0 resident: 79958016 share: 0 rss: 16396288 rss_rlim: 0 CPU usage: start_time: 1171887672 rtime: 0 utime: 269 stime: 0 cutime:245 cstime: 0 timeout: 24 it_real_value: 0 frequency: 40 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 -1226451280 (LWP 20331)] [New Thread -1274545248 (LWP 20336)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 111963
Thread 1 (Thread -1226451280 (LWP 20331))
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 354477 ***