GNOME Bugzilla – Bug 569922
crash in File Browser: Closing window
Last modified: 2009-01-31 00:26:50 UTC
Version: 2.20.0 What were you doing when the application crashed? Closing window Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaFancyCandy Icon Theme: LiNsta-0.3 Memory status: size: 108396544 vsize: 108396544 resident: 48189440 share: 17518592 rss: 48189440 rss_rlim: 4294967295 CPU usage: start_time: 1233358229 rtime: 3555 utime: 3295 stime: 260 cutime:1738 cstime: 304 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ad39a0 (LWP 3694)] (no debugging symbols found) 0xb7fda424 in __kernel_vsyscall ()
+ Trace 212047
Thread 1 (Thread 0xb6ad39a0 (LWP 3694))
----------- .xsession-errors --------------------- (gnome-control-center:4057): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed ** (gnome-control-center:4057): WARNING **: error raised: [load_xbel_store: couldn't load bookmark file [(null)] ] current dist not found in meta-release file could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.PowerManager was not provided by any .service files could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.PowerManager was not provided by any .service files current dist not found in meta-release file could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.PowerManager was not provided by any .service files ** ** ERROR:(fm-tree-model.c:1527):fm_tree_model_unref_node: assertion failed: (parent->dummy_child_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 ***