GNOME Bugzilla – Bug 547121
crash in Open Folder: setting up and connectin...
Last modified: 2008-08-10 20:08:18 UTC
Version: 2.20.0 What were you doing when the application crashed? setting up and connecting to a passwordless SMB share on another computer Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25.10tomacco #1 SMP Tue Jul 8 07:37:45 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 80015360 vsize: 80015360 resident: 28176384 share: 14327808 rss: 28176384 rss_rlim: 4294967295 CPU usage: start_time: 1218324500 rtime: 192 utime: 174 stime: 18 cutime:0 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 0xb6b6a720 (LWP 11287)] (no debugging symbols found) 0xb7f9e424 in __kernel_vsyscall ()
+ Trace 204924
Thread 1 (Thread 0xb6b6a720 (LWP 11287))
----------- .xsession-errors (32323 sec old) --------------------- (firefox-bin:18065): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:18065): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:18065): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:18065): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:18065): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:18065): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:18065): 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 ***