GNOME Bugzilla – Bug 449705
crash in Panel: login
Last modified: 2007-06-21 18:50:31 UTC
Version: 2.18.2 What were you doing when the application crashed? login 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 61161472 vsize: 61161472 resident: 20496384 share: 16617472 rss: 20496384 rss_rlim: 4294967295 CPU usage: start_time: 1182410722 rtime: 38 utime: 31 stime: 7 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 -1208559904 (LWP 2796)] (no debugging symbols found) 0x009b2402 in __kernel_vsyscall ()
+ Trace 142600
Thread 1 (Thread -1208559904 (LWP 2796))
----------- .xsession-errors (6 sec old) --------------------- Creating backend ... Loading x11 FrontEnd module ... GTK Panel of SCIM 1.4.5 ** (gnome-session:2676): WARNING **: Host name lookup failure on localhost. Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running (gnome-panel:2796): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (bug-buddy:2891): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤:元素‘b’已關閉,但開啟中的元素是‘span’ --------------------------------------------------
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 ***