GNOME Bugzilla – Bug 531173
crash in Open Folder: Browesing windows folder...
Last modified: 2008-05-03 10:18:18 UTC
Version: 2.20.0 What were you doing when the application crashed? Browesing windows folder shares. Could open other shares on the same computer and hard drive. I don't think it is a security issue. My Documents is a large share that has a lot of files. Could be a size issue? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77901824 vsize: 77901824 resident: 22769664 share: 14999552 rss: 22769664 rss_rlim: 4294967295 CPU usage: start_time: 1209784683 rtime: 340 utime: 318 stime: 22 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6bf9720 (LWP 3151)] (no debugging symbols found) 0xb760df91 in waitpid () from /lib/libpthread.so.0
+ Trace 196742
Thread 1 (Thread 0xb6bf9720 (LWP 3151))
----------- .xsession-errors (25 sec old) --------------------- ** (gnome-settings-daemon:3120): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Window manager warning: Failed to read saved session file /home/gary/.metacity/sessions/default0.ms: Failed to open file '/home/gary/.metacity/sessions/default0.ms': No such file or directory Initializing gnome-mount extension seahorse nautilus module initialized /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) Window manager warning: last_user_time (3076371504) is greater than comparison timestamp (2898907714). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE Window manager warning: 0x2400003 (Software U) appears to be one of the offending windows with a timestamp of 3076371504. Working around... current dist not found in meta-release file connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! --------------------------------------------------
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 ***