GNOME Bugzilla – Bug 554417
crash in File Browser: open a windows folder
Last modified: 2008-10-04 09:06:33 UTC
Version: 2.20.0 What were you doing when the application crashed? open a windows folder 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: 69812224 vsize: 69812224 resident: 25579520 share: 15695872 rss: 25579520 rss_rlim: 4294967295 CPU usage: start_time: 1222760986 rtime: 275 utime: 259 stime: 16 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 0xb6b0b720 (LWP 4262)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 207563
Thread 1 (Thread 0xb6b0b720 (LWP 4262))
----------- .xsession-errors (14 sec old) --------------------- (gnome-www-browser:4220): GLib-GObject-WARNING **: value "((GaProtocol) 2)" of type `GaProtocol' is invalid or out of range for property `flags' of type `GaProtocol' (gnome-www-browser:4220): GLib-GObject-WARNING **: value "((GaProtocol) 2)" of type `GaProtocol' is invalid or out of range for property `flags' of type `GaProtocol' (gnome-www-browser:4220): GLib-CRITICAL **: g_hash_table_unref: assertion `hash_table != NULL' failed (gnome-www-browser:4220): GLib-CRITICAL **: g_hash_table_unref: assertion `hash_table != NULL' failed Initializing gnome-mount extension seahorse nautilus module initialized 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 ***