GNOME Bugzilla – Bug 545675
crash in Open Folder: trying to browse a verl ...
Last modified: 2008-07-31 12:18:57 UTC
Version: 2.20.0 What were you doing when the application crashed? trying to browse a verl large direcroty on a samba share. Doesn't happen with any other subdirectory on the same share. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 84856832 vsize: 84856832 resident: 32886784 share: 15945728 rss: 32886784 rss_rlim: 4294967295 CPU usage: start_time: 1217503878 rtime: 7205 utime: 6356 stime: 849 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b46720 (LWP 3641)] [New Thread 0xb5b60b90 (LWP 3905)] (no debugging symbols found) 0xb7f77424 in __kernel_vsyscall ()
+ Trace 204259
Thread 1 (Thread 0xb6b46720 (LWP 3641))
----------- .xsession-errors (507 sec old) --------------------- ** (gnome-settings-daemon:3617): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory ** (x-session-manager:3536): WARNING **: Host name lookup failure on localhost. Window manager warning: Failed to read saved session file /home/chris/.metacity/sessions/default0.ms: Failed to open file '/home/chris/.metacity/sessions/default0.ms': No such file or directory seahorse nautilus module initialized Initializing gnome-mount extension Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x2400020 (06/26/2008); these messages lack timestamps and therefore suck. ** (nautilus:3641): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Main%20Storage"), please tell the gnome-vfs mailing list. 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 ***