GNOME Bugzilla – Bug 491178
crash in Panel: Logged out, and back int...
Last modified: 2007-10-29 13:50:15 UTC
Version: 2.18.3 What were you doing when the application crashed? Logged out, and back into desktop after installing software updates. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glider Icon Theme: Echo Memory status: size: 100954112 vsize: 100954112 resident: 43094016 share: 39698432 rss: 43094016 rss_rlim: 4294967295 CPU usage: start_time: 1193604791 rtime: 102 utime: 84 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208482080 (LWP 7089)] 0x00110402 in __kernel_vsyscall ()
+ Trace 173512
Thread 1 (Thread -1208482080 (LWP 7089))
----------- .xsession-errors (18 sec old) --------------------- SESSION_MANAGER=local/unix:/tmp/.ICE-unix/6965 Initializing nautilus-open-terminal extension Initializing nautilus-image-converter extension winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running Window manager warning: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed (bluetooth-applet:7099): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-panel:7089): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed /usr/bin/puplet:371: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed gtk.main() (nm-applet:7108): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:7090): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 446183 ***