GNOME Bugzilla – Bug 540011
crash in Open Folder: Browsing to .mozilla/def...
Last modified: 2008-06-24 22:50:17 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing to .mozilla/default/profile_es0efw in server Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: Clearlooks Icon Theme: gnome Memory status: size: 82669568 vsize: 82669568 resident: 27709440 share: 16084992 rss: 27709440 rss_rlim: 4294967295 CPU usage: start_time: 1214330962 rtime: 919 utime: 847 stime: 72 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 0xb6bff720 (LWP 4438)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201284
Thread 1 (Thread 0xb6bff720 (LWP 4438))
----------- .xsession-errors (63 sec old) --------------------- (gnome-terminal:3374): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ** (nautilus:3200): WARNING **: No description found for mime type "x-directory/smb-share" (file is "ARCWIN"), 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!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:4438): WARNING **: No description found for mime type "x-directory/smb-share" (file is "HOME"), please tell the gnome-vfs mailing list. --------------------------------------------------
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 ***