GNOME Bugzilla – Bug 448509
crash in Panel: ソフトアップデート後、KDE。XFCEなど動作モ...
Last modified: 2007-06-17 16:42:48 UTC
Version: 2.18.2 What were you doing when the application crashed? ソフトアップデート後、KDE。XFCEなど動作モード拡大を実施。再度、電源オフから立ち上げを行ったところ、タイトル・メニューバーの表示が出なくなった。幾度行っても同じ。 Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 53530624 vsize: 53530624 resident: 22208512 share: 17666048 rss: 22208512 rss_rlim: 4294967295 CPU usage: start_time: 1182092648 rtime: 43 utime: 35 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208699168 (LWP 3391)] (no debugging symbols found) 0x00ac7402 in __kernel_vsyscall ()
+ Trace 141673
Thread 1 (Thread -1208699168 (LWP 3391))
----------- .xsession-errors (10 sec old) --------------------- SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3283 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 (bluetooth-applet:3398): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ウィンドウ・マネージャの警告: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:3420): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-panel:3391): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3395): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 446183 ***