Version: 2.20.0

What were you doing when the application crashed?
same again, browsing a backup of my home directory


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 90320896 vsize: 90320896 resident: 34107392 share: 15237120 rss: 34107392 rss_rlim: 4294967295
CPU usage: start_time: 1211998729 rtime: 486 utime: 442 stime: 44 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b07940 (LWP 26850)]
[New Thread 0xb54eab90 (LWP 26954)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 198881

----------- .xsession-errors (27854 sec old) ---------------------
Unknown parameter encountered: "domain admin users"
Ignoring unknown parameter "domain admin users"
warning: configuration item media.audio_cd.cddb_cachedir points to a non-existent location /home/akm/.xine/cddbcache
warning: configuration item media.capture.save_dir points to a non-existent location 
warning: configuration item media.dvd.device points to a non-existent location /dev/dvd
warning: configuration item media.dvd.raw_device points to a non-existent location /dev/rdvd
warning: configuration item media.dvd.css_cache_path points to a non-existent location /home/akm/.dvdcss/
warning: configuration item media.video4linux.radio_device points to a non-existent location /dev/radio0
warning: configuration item media.video4linux.video_device points to a non-existent location /dev/video0
warning: configuration item media.wintv_pvr.device points to a non-existent location /dev/video0
warning: configuration item subtitles.separate.font_freetype points to a non-existent location 
lirc: cannot initialise - disabling remote control
lirc: maybe lircd isn't running or you can't connect to the socket?
...Too much output, ignoring rest...
--------------------------------------------------