Version: 2.20.0

What were you doing when the application crashed?
Nautilus regular reboot. This and the previous report I sent are actually nothing new, they've been happening for so many months I can't remember how far back, and it's always during some reboot/shutdown command from inside gnome, happens about at least 70% of the time. I guess I kept thinking it would go away with the next update. Don't know why I suddenly decided to report them, but here it is.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.3-6224w #1 SMP Sun Mar 2 03:24:18 CET 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SlicknesS
Icon Theme: black-white_2-Gloss

Memory status: size: 463966208 vsize: 463966208 resident: 23527424 share: 16093184 rss: 23527424 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218965640 rtime: 70 utime: 56 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x2b3cda871b40 (LWP 3677)]
0x00002b3cd33f25ff in waitpid () from /lib/libpthread.so.0

+ Trace 205263

----------- .xsession-errors ---------------------
 3654 ?        S      0:00 keytouchd
  PID TTY      STAT   TIME COMMAND
 3654 ?        S      0:00 keytouchd
  PID TTY      STAT   TIME COMMAND
 3654 ?        S      0:00 keytouchd
  PID TTY      STAT   TIME COMMAND
 3654 ?        S      0:00 keytouchd
  PID TTY      STAT   TIME COMMAND
 3654 ?        S      0:00 keytouchd
  PID TTY      STAT   TIME COMMAND
 3654 ?        S      0:00 keytouchd
  PID TTY      STAT   TIME COMMAND
 3654 ?        S      0:00 keytouchd
  PID TTY      STAT   TIME COMMAND
 3654 ?        S      0:00 keytouchd
--------------------------------------------------