Version: 0.10.1

What were you doing when the application crashed?
I started tvtime and then closed rhythmbox


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: CleanOrange
Icon Theme: glass-icons

Memory status: size: 95150080 vsize: 95150080 resident: 27856896 share: 14290944 rss: 27856896 rss_rlim: 4294967295
CPU usage: start_time: 1193274348 rtime: 8387 utime: 8193 stime: 194 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(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 0xb6bfb6c0 (LWP 13649)]
[New Thread 0xb56deb90 (LWP 13654)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 172668

----------- .xsession-errors (2372 sec old) ---------------------
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
QImage::setPixel: x=1 out of range
...Too much output, ignoring rest...
--------------------------------------------------