GNOME Bugzilla – Bug 354477
crash in Terminal: I started a new terminal...
Last modified: 2007-07-15 09:51:31 UTC
Version: 2.15.4 What were you doing when the application crashed? I started a new terminal from an icon on the panel Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 Memory status: size: 58028032 vsize: 0 resident: 58028032 share: 0 rss: 18919424 rss_rlim: 0 CPU usage: start_time: 1157303233 rtime: 0 utime: 3182 stime: 0 cutime:2801 cstime: 0 timeout: 381 it_real_value: 0 frequency: 6934 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 -1225582928 (LWP 5106)] [New Thread -1249989728 (LWP 5110)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 71646
Thread 1 (Thread -1225582928 (LWP 5106))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. This seems to be deep inside gtk...
This is what Ubuntu's Bug Buddy gave me.. and it's not easy to reproduce, it just crashes every now and then. I see it's been upgraded as well (not during the crash though).. it might be fixed already.
I don't know how this is done in Ubuntu, but maybe you could install a gtk package with debugging symbols and wait for the crash ;-)
*** Bug 361832 has been marked as a duplicate of this bug. ***
*** Bug 362977 has been marked as a duplicate of this bug. ***
*** Bug 363892 has been marked as a duplicate of this bug. ***
*** Bug 367650 has been marked as a duplicate of this bug. ***
*** Bug 368161 has been marked as a duplicate of this bug. ***
*** Bug 368260 has been marked as a duplicate of this bug. ***
*** Bug 368181 has been marked as a duplicate of this bug. ***
*** Bug 369107 has been marked as a duplicate of this bug. ***
confirming...
*** Bug 371965 has been marked as a duplicate of this bug. ***
*** Bug 375075 has been marked as a duplicate of this bug. ***
*** Bug 376328 has been marked as a duplicate of this bug. ***
*** Bug 378257 has been marked as a duplicate of this bug. ***
*** Bug 379657 has been marked as a duplicate of this bug. ***
*** Bug 381306 has been marked as a duplicate of this bug. ***
*** Bug 384648 has been marked as a duplicate of this bug. ***
*** Bug 385548 has been marked as a duplicate of this bug. ***
*** Bug 387792 has been marked as a duplicate of this bug. ***
*** Bug 389512 has been marked as a duplicate of this bug. ***
*** Bug 392318 has been marked as a duplicate of this bug. ***
*** Bug 393216 has been marked as a duplicate of this bug. ***
*** Bug 393760 has been marked as a duplicate of this bug. ***
*** Bug 393775 has been marked as a duplicate of this bug. ***
*** Bug 375467 has been marked as a duplicate of this bug. ***
*** Bug 391388 has been marked as a duplicate of this bug. ***
*** Bug 394651 has been marked as a duplicate of this bug. ***
*** Bug 395886 has been marked as a duplicate of this bug. ***
*** Bug 396646 has been marked as a duplicate of this bug. ***
*** Bug 396766 has been marked as a duplicate of this bug. ***
*** Bug 398647 has been marked as a duplicate of this bug. ***
*** Bug 400274 has been marked as a duplicate of this bug. ***
*** Bug 400342 has been marked as a duplicate of this bug. ***
*** Bug 401399 has been marked as a duplicate of this bug. ***
*** Bug 401977 has been marked as a duplicate of this bug. ***
We need a good stack trace with debugging symbols to sort this out. It may well be that this is just a dup of another bug we've fixed recently. Please reporters, 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 401765 has been marked as a duplicate of this bug. ***
*** Bug 402275 has been marked as a duplicate of this bug. ***
I tried hard to crash it again after installing gnome-terminal debuging symbol packed. I will keep trying from time to time.
*** Bug 402577 has been marked as a duplicate of this bug. ***
*** Bug 403450 has been marked as a duplicate of this bug. ***
*** Bug 403482 has been marked as a duplicate of this bug. ***
*** Bug 405751 has been marked as a duplicate of this bug. ***
*** Bug 406054 has been marked as a duplicate of this bug. ***
*** Bug 408020 has been marked as a duplicate of this bug. ***
*** Bug 408242 has been marked as a duplicate of this bug. ***
*** Bug 408607 has been marked as a duplicate of this bug. ***
*** Bug 409439 has been marked as a duplicate of this bug. ***
*** Bug 409578 has been marked as a duplicate of this bug. ***
*** Bug 410004 has been marked as a duplicate of this bug. ***
*** Bug 410676 has been marked as a duplicate of this bug. ***
*** Bug 412050 has been marked as a duplicate of this bug. ***
*** Bug 412054 has been marked as a duplicate of this bug. ***
*** Bug 412412 has been marked as a duplicate of this bug. ***
*** Bug 412650 has been marked as a duplicate of this bug. ***
*** Bug 413223 has been marked as a duplicate of this bug. ***
*** Bug 415442 has been marked as a duplicate of this bug. ***
*** Bug 418103 has been marked as a duplicate of this bug. ***
*** Bug 419020 has been marked as a duplicate of this bug. ***
*** Bug 420046 has been marked as a duplicate of this bug. ***
*** Bug 421381 has been marked as a duplicate of this bug. ***
*** Bug 423387 has been marked as a duplicate of this bug. ***
I'm closing this because all the duplicates are from version 2.16.1 or older. Please reopen if you can reproduce this with newer version and can provide a stack trace with debugging symbols.