GNOME Bugzilla – Bug 537478
crash in Computer: exploration d'un partage...
Last modified: 2008-06-09 22:21:19 UTC
Version: 2.20.0 What were you doing when the application crashed? exploration d'un partage SAMBA sur NAS 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: Amaranth Icon Theme: Amaranth Memory status: size: 76603392 vsize: 76603392 resident: 21213184 share: 15269888 rss: 21213184 rss_rlim: 4294967295 CPU usage: start_time: 1213046998 rtime: 166 utime: 154 stime: 12 cutime:0 cstime: 0 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 0xb6bfb720 (LWP 5273)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199972
Thread 1 (Thread 0xb6bfb720 (LWP 5273))
----------- .xsession-errors (66 sec old) --------------------- Checking for Composite extension: present. Comparing resolution (1024x768) to maximum 3D texture size (2048): Passed. Checking for nVidia: not present. Checking for FBConfig: present. Checking for Xgl: not present. Starting gtk-window-decorator ** (nautilus:5273): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:5273): WARNING **: Can not calculate _NET_NUMBER_OF_DESKTOPS ** (nautilus:5273): WARNING **: Can not get _NET_WORKAREA ** (nautilus:5273): WARNING **: Can not determine workarea, guessing at layout /usr/bin/compiz.real (cube) - Warn: Failed to load slide: freedesktop --------------------------------------------------
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 522534 ***