GNOME Bugzilla – Bug 552063
crash in Open Folder:
Last modified: 2008-09-13 09:43:31 UTC
Version: 2.20.0 What were you doing when the application crashed? 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: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 61198336 vsize: 61198336 resident: 26767360 share: 15425536 rss: 26767360 rss_rlim: 4294967295 CPU usage: start_time: 1221274617 rtime: 502 utime: 474 stime: 28 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 0xb6ada720 (LWP 7309)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 206717
Thread 1 (Thread 0xb6ada720 (LWP 7309))
----------- .xsession-errors (7 sec old) --------------------- ** (epiphany-browser:7126): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x280001e (Archive Ma) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized Window manager warning: Invalid WM_TRANSIENT_FOR window 0x85 specified for 0x1000297 (). Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:7309): WARNING **: No description found for mime type "x-directory/smb-share" (file is "G"), 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 ***