GNOME Bugzilla – Bug 476482
crash in System Log:
Last modified: 2007-09-15 11:55:57 UTC
Version: 2.18.0 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 37855232 vsize: 37855232 resident: 12861440 share: 8339456 rss: 12861440 rss_rlim: 4294967295 CPU usage: start_time: 1189669647 rtime: 904 utime: 842 stime: 62 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1209121056 (LWP 3546)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 162567
Thread 1 (Thread -1209121056 (LWP 3546))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/sephire.harshnet:/tmp/.ICE-unix/3167 ** (gnome-session:3167): WARNING **: Host name lookup failure on localhost. ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running error getting update info: failure: repodata/primary.sqlite.bz2 from fedora: [Errno 256] No more mirrors to try. error getting update info: failure: repodata/primary.sqlite.bz2 from fedora: [Errno 256] No more mirrors to try. Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3951-2123402409-1189670060 --active --geometry 80x24+-5105+97 --title root@sephire:~ --wor --------------------------------------------------
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 442846 ***