GNOME Bugzilla – Bug 507657
crash in System Log:
Last modified: 2008-02-13 10:26:38 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: redhat release 5 Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 38633472 vsize: 38633472 resident: 20779008 share: 15396864 rss: 20779008 rss_rlim: 4294967295 CPU usage: start_time: 1199626973 rtime: 504 utime: 470 stime: 34 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 -1208367392 (LWP 3484)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184272
Thread 1 (Thread -1208367392 (LWP 3484))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3162 error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: updates. Please verify its path and try again /usr/share/system-config-display/system-config-display: line 2: 3447 Segmentation fault python2 /usr/share/system-config-display/xconf.py $@ /usr/share/system-config-display/system-config-display: line 2: 3496 Segmentation fault python2 /usr/share/system-config-display/xconf.py $@ Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3395--947295060-1199626625 --active --geometry 80x24+0+24 --title root@localhost:~ --worki --------------------------------------------------
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 ***