GNOME Bugzilla – Bug 516263
crash in System Log: 外からリモートアクセスしていました
Last modified: 2008-02-15 16:50:14 UTC
Version: 2.18.1 What were you doing when the application crashed? 外からリモートアクセスしていました Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 62119936 vsize: 62119936 resident: 36982784 share: 17346560 rss: 36982784 rss_rlim: 4294967295 CPU usage: start_time: 1202912472 rtime: 290 utime: 278 stime: 12 cutime:1 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 -1208879392 (LWP 11089)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189085
Thread 1 (Thread -1208879392 (LWP 11089))
----------- .xsession-errors (4221 sec old) --------------------- ConsoleKit console-kit-daemon (pid 2536) を実行中... ConsoleKit console-kit-daemon (pid 2536) を実行中... ConsoleKit console-kit-daemon (pid 2536) を実行中... /usr/share/system-config-httpd/CheckList.py:12: DeprecationWarning: use gtk.TreeView CList.__init__ (self, 2) /usr/share/system-config-httpd/ApacheConf.py:122: DeprecationWarning: use gtk.TreeView gtk.CList.__init__ (self, 3, [_("Error Code"), _("Behavior"), _("Location")]) --- Hash table keys for warning below: --> file:///root (nautilus:11124): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --------------------------------------------------
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 ***