GNOME Bugzilla – Bug 561506
crash in Computer: I pushed the button to g...
Last modified: 2008-11-19 18:01:30 UTC
Version: 2.20.0 What were you doing when the application crashed? I pushed the button to go to previous directory Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist Memory status: size: 135249920 vsize: 135249920 resident: 73744384 share: 17911808 rss: 73744384 rss_rlim: 4294967295 CPU usage: start_time: 1227084696 rtime: 4345 utime: 4059 stime: 286 cutime:0 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6af0710 (LWP 3178)] [New Thread 0xb40ffb90 (LWP 10884)] 0xb7fe3424 in __kernel_vsyscall ()
+ Trace 210004
Thread 1 (Thread 0xb6af0710 (LWP 3178))
----------- .xsession-errors --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) (epiphany-browser:10724): GLib-GObject-WARNING **: value "((GaProtocol) 2)" of type `GaProtocol' is invalid or out of range for property `flags' of type `GaProtocol' ** (epiphany-browser:10724): WARNING **: Unable to delete /home/ricard/.gnome2/epiphany/favicon_cache/d38e98ab0e6b42777b7e85acc5aa0992 ** (nautilus:3178): WARNING **: No s'ha trobat la descripció del tipus mime «x-directory/smb-share» (el fitxer és «D»), informeu-ne a la llista de correu del gnome-vfs. connection_message_func(): Callback CALLBACK: fill-authentication!!! ** ** ERROR:(fm-tree-model.c:1531):fm_tree_model_unref_node: assertion failed: (node->ref_count > 0) --------------------------------------------------
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 512040 ***