GNOME Bugzilla – Bug 507027
crash in System Log: nothing
Last modified: 2008-02-13 10:26:28 UTC
Version: 2.18.1 What were you doing when the application crashed? nothing 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.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 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: 95690752 vsize: 95690752 resident: 46759936 share: 4132864 rss: 46759936 rss_rlim: 4294967295 CPU usage: start_time: 1197918300 rtime: 49403 utime: 41770 stime: 7633 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 -1208264992 (LWP 2572)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183913
Thread 1 (Thread -1208264992 (LWP 2572))
----------- .xsession-errors (9 sec old) --------------------- (nautilus:18468): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed (nautilus:18468): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed ConsoleKit console-kit-daemon (pid 1774) is running... ConsoleKit console-kit-daemon (pid 1774) is running... ConsoleKit console-kit-daemon (pid 1774) is running... squid squid dead but pid file exists squid squid dead but pid file exists Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-2636-671876331-1197918373 --active --geometry 80x24+0+24 --title root@proxy1:~ --working-d I/O error : No space left on device --------------------------------------------------
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 ***