GNOME Bugzilla – Bug 420355
crash in Power Manager: The Automatic Updater wa...
Last modified: 2007-03-20 21:07:03 UTC
What were you doing when the application crashed? The Automatic Updater was Resolving dependencies for updates(229) Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.91 2007-02-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.2997.fc7 #1 SMP Fri Mar 16 22:15:07 EDT 2007 ppc64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: Enforcing Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 63688704 vsize: 63688704 resident: 12054528 share: 8523776 rss: 12054528 rss_rlim: 18446744073709551615 CPU usage: start_time: 1174261621 rtime: 135 utime: 76 stime: 59 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-power-manager' (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 4155703296 (LWP 2751)] (no debugging symbols found) 0x0eb001a8 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 120208
Thread 1 (Thread 4155703296 (LWP 2751))
----------- .xsession-errors (49 sec old) --------------------- Checking deps for NetworkManager-gnome.ppc 1-0.6.5-0.4.svn2474.fc7 - u Checking deps for mailx.ppc 0-8.1.1-46.fc7 - u Checking deps for perl.ppc64 4-5.8.8-12.fc7 - None Checking deps for cairo.ppc64 0-1.4.0-1.fc7 - u Checking deps for tcpdump.ppc 14-3.9.5-3.fc7 - u Checking deps for bzip2.ppc 0-1.0.4-8.fc7 - u Checking deps for texinfo.ppc 0-4.8-15 - u Checking deps for avahi.ppc64 0-0.6.16-3.fc7 - None Checking deps for binutils.ppc 0-2.17.50.0.12-3 - u Checking deps for perl.ppc64 4-5.8.8-15.fc7 - u Checking deps for libvolume_id.ppc 0-104-2 - None Checking deps for xorg-x11-drv-s3.ppc 0-0.5.0-2.fc7 - None Checking deps for gnome-speech.ppc 0-0.4.10-1.fc7 - u Checking deps for xorg-x11-drivers.ppc 0-7.2-2.fc7 - None Checking deps for file-libs.ppc 0-4.19-4.fc7 - None --------------------------------------------------
*** This bug has been marked as a duplicate of 420419 ***