GNOME Bugzilla – Bug 516516
crash in System Log: Shutting down system - r...
Last modified: 2008-02-15 16:50:24 UTC
Version: 2.18.1 What were you doing when the application crashed? Shutting down system - restart in fact. Numerous apps still open File browser, log viewer, service config and text editor 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 114995200 vsize: 114995200 resident: 90726400 share: 16543744 rss: 90726400 rss_rlim: 4294967295 CPU usage: start_time: 1203011293 rtime: 500 utime: 453 stime: 47 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 -1208613152 (LWP 8171)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189220
Thread 1 (Thread -1208613152 (LWP 8171))
----------- .xsession-errors --------------------- Error - cannot end transaction. Rolling back... warning: .dynamic section for "/usr/lib/libgssapi_krb5.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libkrb5.so.3" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libk5crypto.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libkrb5support.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 ***