crash in Terminal: I had added gnome-termin...
Submitted by ubu..@..3s.com
Link to original bug (#357071)
Description
Version: 2.16.0
What were you doing when the application crashed? I had added gnome-terminal to the gnome panel as a launcher. I did this by right-clicking on the menu entry and choosing "Add to panel" or however it's termed.
It crashes consistently when launching from the panel.
Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0
Memory status: size: 20303872 vsize: 0 resident: 20303872 share: 0 rss: 7356416 rss_rlim: 0 CPU usage: start_time: 1158856212 rtime: 0 utime: 24 stime: 0 cutime:21 cstime: 0 timeout: 3 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 -1226299728 (LWP 4790)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
`#0` 0xffffe410 in __kernel_vsyscall ()
`#1` 0xb77cb313 in __waitpid_nocancel ()
from /lib/tls/i686/cmov/libpthread.so.0
`#2` 0xb7f171b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
`#3` <signal handler called>
`#4` 0xb7f7a521 in ?? () from /lib/ld-linux.so.2
`#5` 0x080f5ac0 in ?? ()
`#6` 0x90000001 in ?? ()
`#7` 0x00000000 in ?? ()
Thread 1 (Thread -1226299728 (LWP 4790)):
`#0` 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
`#1` 0xb77cb313 in __waitpid_nocancel ()
from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
`#2` 0xb7f171b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
`#3` <signal handler called>
No symbol table info available.
`#4` 0xb7f7a521 in ?? () from /lib/ld-linux.so.2
No symbol table info available.
`#5` 0x080f5ac0 in ?? ()
No symbol table info available.
`#6` 0x90000001 in ?? ()
No symbol table info available.
`#7` 0x00000000 in ?? ()
No symbol table info available.
`#0` 0xffffe410 in __kernel_vsyscall ()
Version: 2.16.x
Resolution: RESOLVED INVALID