GNOME Bugzilla – Bug 528537
crash in Open Folder:
Last modified: 2008-04-17 11:04:34 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 71872512 vsize: 71872512 resident: 22548480 share: 15208448 rss: 22548480 rss_rlim: 4294967295 CPU usage: start_time: 1208423145 rtime: 229 utime: 211 stime: 18 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 0xb6bf0720 (LWP 4740)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 195442
Thread 1 (Thread 0xb6bf0720 (LWP 4740))
----------- .xsession-errors (12 sec old) --------------------- seahorse nautilus module initialized Initializing gnome-mount extension ** (nm-applet:4763): WARNING **: <WARN> hal_net_physdev_cb(): dbus returned an error. (org.freedesktop.Hal.NoSuchProperty) No property net.physical_device on device with id /org/freedesktop/Hal/devices/net_00_1c_23_34_79_32 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (gnome-terminal:6453): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ** (nautilus:4740): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Tech"), please tell the gnome-vfs mailing list. connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522534 ***