GNOME Bugzilla – Bug 397126
crash in Terminal: upgrading to edgy
Last modified: 2007-01-29 07:24:12 UTC
Version: 2.16.1 What were you doing when the application crashed? upgrading to edgy Distribution: Ubuntu 6.06 (dapper) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 32866304 vsize: 0 resident: 32866304 share: 0 rss: 10805248 rss_rlim: 0 CPU usage: start_time: 1167436308 rtime: 0 utime: 27388 stime: 0 cutime:24524 cstime: 0 timeout: 2864 it_real_value: 0 frequency: 0 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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 102593
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!
This reliably happens to me when upgrading a machine from Ubuntu 6.06 ("dapper") to Ubuntu 6.10 ("edgy"). At some point in the upgrade process, a large number of Gnome components start failing in bizarre and unexpected ways. My guess would be that this is due to mismatches between libraries as some have been upgraded and others have not yet been, but who knows. I am sorry to bother you with it, I thought I was reporting it to Ubuntu. The BugBuddy GUI that automatically pops up seemed to indicate that the bug is going to be reported to Ubuntu, not Gnome. In fact, I believe BugBuddy guided me through the process of reporting the same bug to Gnome once before. I've seen this happen on two different machines, in the process of upgrading from Edgy to Dapper. I am reasonably certain that if you install Ubuntu 6.06 and then try to upgrade, you too will experience this crash. However, I don't really have the time to reinstall Ubuntu 6.06 on my machine and then run the entire upgrade process in a debugger to get a stack trace. Thanks for getting back to me about this. Sorry to have wasted your time.
We love to hear from users, even if it is on the sad occasion of bugs! ;-) It would be very useful if you reported this issue to Ubuntu. Thanks!