GNOME Bugzilla – Bug 410598
crash in Terminal: said yes to overwrite ex...
Last modified: 2007-02-27 19:49:31 UTC
Version: 2.16.1 What were you doing when the application crashed? said yes to overwrite exisiting profile with a new one of same name. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 73400320 vsize: 0 resident: 73400320 share: 0 rss: 17510400 rss_rlim: 0 CPU usage: start_time: 1172098959 rtime: 0 utime: 208 stime: 0 cutime:194 cstime: 0 timeout: 14 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) [Thread debugging using libthread_db enabled] [New Thread -1226291536 (LWP 6247)] [New Thread -1267782752 (LWP 6251)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 112737
Thread 1 (Thread -1226291536 (LWP 6247))
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!
To repeat: make profile called "ser". Close teminal, attempt to make another profile also called "ser", then say yes when the prompt: "You already have a profile called "ser". Do you want to create another profile with the same name?" debug trace as requested: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 72765440 vsize: 0 resident: 72765440 share: 0 rss: 16343040 rss_rlim: 0 CPU usage: start_time: 1172605065 rtime: 0 utime: 101 stime: 0 cutime:95 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226418512 (LWP 5160)] [New Thread -1267909728 (LWP 5164)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 114398
Thread 1 (Thread -1226418512 (LWP 5160))
Thanks for the info! Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 363609 ***