Version: 2.20.3

What were you doing when the application crashed?
I just put a DVD to the drive. Next the totem came up. The dvd is a movie dvd.  


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 40517632 vsize: 40517632 resident: 17735680 share: 13045760 rss: 17735680 rss_rlim: 4294967295
CPU usage: start_time: 1203974232 rtime: 40 utime: 36 stime: 4 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6dce6b0 (LWP 6203)]
[New Thread 0xb6609b90 (LWP 6205)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 190440

----------- .xsession-errors (363 sec old) ---------------------
  (Details: serial 2656726 error_code 13 request_code 59 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnomebaker' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 2656724 error_code 16 request_code 4 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
--------------------------------------------------