Version: 2.18.3

What were you doing when the application crashed?
Ran a script that sets up and enters a chroot environment. Effectively, mounts a normal filesystem, then binds /home and /dev into it, and mounts /proc and /sys within it.


Distribution: Unknown
Gnome Release: 2.18.3 2007-07-06 (GNOME.Org)
BugBuddy Version: 2.18.1

System: Linux 2.6.21.5 #3 PREEMPT Wed Jun 13 19:49:00 NZST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 24182784 vsize: 24182784 resident: 14127104 share: 10248192 rss: 14127104 rss_rlim: 4294967295
CPU usage: start_time: 1183779489 rtime: 57 utime: 47 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225881920 (LWP 1416)]
0xffffe410 in ?? ()

+ Trace 146251

Thread 1 (Thread -1225881920 (LWP 1416)):
#-1 0xffffe410 in ?? ()
No symbol table info available.
#-1 0xffffe410 in ?? ()


----------- .xsession-errors ---------------------
(gnome-terminal:1528): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:1528): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:1528): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:1528): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:1528): Vte-WARNING **: DECSET/DECRESET mode 1034 not recognized, ignoring.
Backtrace limit of 200 exceeded
/usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file:
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
--------------------------------------------------