GNOME Bugzilla – Bug 464302
crash in System Log:
Last modified: 2007-09-25 18:47:07 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-07-31 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-gentoo-r2 #2 SMP PREEMPT Tue Aug 7 12:30:46 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: Buuf Memory status: size: 208056320 vsize: 208056320 resident: 31109120 share: 19890176 rss: 31109120 rss_rlim: 18446744073709551615 CPU usage: start_time: 1186487391 rtime: 757 utime: 740 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/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 47495895540848 (LWP 5721)] 0x00002b327eb6d53e in waitpid () from /lib/libpthread.so.0
+ Trace 153437
Thread 1 (Thread 47495895540848 (LWP 5721))
----------- .xsession-errors --------------------- ** Message: drive = 688400 ** Message: volume = 68f0a0 ** Message: drive = 688820 ** Message: volume = 0 ERROR: whilst scanning summary file (trackerd:5482): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (trackerd:5482): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (trackerd:5482): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (trackerd:5482): GLib-CRITICAL **: g_hash_table_size: assertion `hash_table != NULL' failed No running windows found Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-5731-382702921-1186487483 --active --geometry 80x24+4+72 --title root@mars:~ --working-dir --------------------------------------------------
Gnome-system-log crashes while shutting down the system
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 ***