GNOME Bugzilla – Bug 524836
crash in Home Folder:
Last modified: 2008-03-29 18:23:15 UTC
What were you doing when the application crashed? Distribution: Red Hat Enterprise Linux AS release 3 (Taroon) Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 140533760 vsize: 140533760 resident: 31215616 share: 16134144 rss: 31215616 rss_rlim: 4294967295 CPU usage: start_time: 1206699106 rtime: 2860 utime: 2656 stime: 204 cutime:112 cstime: 38 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 0xb6c2b720 (LWP 3453)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 193549
Thread 1 (Thread 0xb6c2b720 (LWP 3453))
----------- .xsession-errors (8 sec old) --------------------- Sample Rate : 44100 Time: 00:00.00 [00:00.76] of 00:00.76 (0.00%) Samples out: 0 Clips: 0 Time: 00:00.56 [00:00.21] of 00:00.76 (72.9%) Samples out: 26.3k Clips: 0 Time: 00:00.74 [00:00.02] of 00:00.76 (97.2 Done. Input File : '/usr/share/amsn/skins/default/sounds/online.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 2 Sample Rate : 44100 Time: 00:00.00 [00:00.81] of 00:00.81 (0.00%) Samples out: 0 Clips: 0 Time: 00:00.56 [00:00.26] of 00:00.81 (68.4%) Samples out: 26.3k Clips: 0 Time: 00:00.74 [00:00.07] of 00:00.81 (91.3 Done. (nautilus:3453): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 355018 ***