GNOME Bugzilla – Bug 485598
crash in System Log: Trying to apply package ...
Last modified: 2007-10-12 23:59:37 UTC
Version: 2.18.0 What were you doing when the application crashed? Trying to apply package updates 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:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 276860928 vsize: 276860928 resident: 14077952 share: 8454144 rss: 14077952 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192074137 rtime: 267 utime: 251 stime: 16 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496344464 (LWP 3073)] (no debugging symbols found) 0x000000309a40d865 in waitpid () from /lib64/libpthread.so.0
+ Trace 169396
Thread 1 (Thread 46912496344464 (LWP 3073))
----------- .xsession-errors (193 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2817 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name error getting update info: Cannot open/read repomd.xml file for repository: fedora Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3200003 (/var/log/m); these messages lack timestamps and therefore suck. Loading "installonlyn" plugin Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-7&arch=x86_64 error was [Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')> --------------------------------------------------
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 ***