GNOME Bugzilla – Bug 479956
crash in System Log: logging out
Last modified: 2007-09-25 18:47:57 UTC
Version: 2.18.0 What were you doing when the application crashed? logging out 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 37421056 vsize: 37421056 resident: 13213696 share: 9084928 rss: 13213696 rss_rlim: 4294967295 CPU usage: start_time: 1190665025 rtime: 364 utime: 203 stime: 161 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 -1208953120 (LWP 2636)] (no debugging symbols found) 0x00fc8402 in __kernel_vsyscall ()
+ Trace 165178
Thread 1 (Thread -1208953120 (LWP 2636))
----------- .xsession-errors (6 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/hecomp-fc7:/tmp/.ICE-unix/2434 /usr/share/system-config-selinux/system-config-selinux.py:69: Warning: IA__g_object_get_valist: object class `GnomeProgram' has no property named `default-icon' xml = gtk.glade.XML ("/usr/share/system-config-selinux/system-config-selinux.glade", domain=PROGNAME) Loading "installonlyn" plugin Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-2654-395569837-1190665114 --active --geometry 80x24+0+49 --title heathe@hecomp-fc7:~ --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 ***