GNOME Bugzilla – Bug 540163
crash in Open Folder: Just mounted a windows s...
Last modified: 2008-06-25 18:03:04 UTC
Version: 2.20.0 What were you doing when the application crashed? Just mounted a windows share, and started browsing it. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Tue May 27 15:38:35 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 75001856 vsize: 75001856 resident: 23859200 share: 15339520 rss: 23859200 rss_rlim: 4294967295 CPU usage: start_time: 1214405231 rtime: 337 utime: 313 stime: 24 cutime:3 cstime: 0 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 0xb6aa3720 (LWP 6138)] (no debugging symbols found) 0xb7ee5424 in __kernel_vsyscall ()
+ Trace 201366
Thread 1 (Thread 0xb6aa3720 (LWP 6138))
----------- .xsession-errors (6490 sec old) --------------------- (firefox-bin:5029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ...Too much output, ignoring rest... --------------------------------------------------
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 ***