GNOME Bugzilla – Bug 420958
crash in Power Manager: yum upgrade
Last modified: 2007-03-21 19:57:00 UTC
What were you doing when the application crashed? yum upgrade Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.18.0 2007-03-19 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.2997.fc7 #1 SMP Fri Mar 16 22:29:02 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299901 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 49696768 vsize: 49696768 resident: 4837376 share: 3330048 rss: 4837376 rss_rlim: 4294967295 CPU usage: start_time: 1174473524 rtime: 8 utime: 5 stime: 3 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208453408 (LWP 3069)] (no debugging symbols found) 0x0066d402 in __kernel_vsyscall ()
+ Trace 120721
Thread 1 (Thread -1208453408 (LWP 3069))
----------- .xsession-errors (2250 sec old) --------------------- Checking deps for festival.i386 0-1.96-0.11.fc7 - u Checking deps for iproute.i386 0-2.6.20-2.fc7 - u Checking deps for nash.i386 0-6.0.8-1 - None Checking deps for webalizer.i386 0-2.01_10-31 - None Checking deps for SDL.i386 0-1.2.10-9 - None Checking deps for gnome-desktop-devel.i386 0-2.18.0-1.fc7 - None Checking deps for xorg-x11-drv-siliconmotion.i386 0-1.4.1-3.fc7 - None Checking deps for SDL-devel.i386 0-1.2.10-9 - None Checking deps for gnome-desktop-devel.i386 0-2.18.0-2.fc7 - u Checking deps for samba-client.i386 0-3.0.24-4.fc7 - None Checking deps for java-1.5.0-gcj.i386 0-1.5.0.0-6.fc7 - u Checking deps for selinux-policy.noarch 0-2.5.8-5.fc7 - None Checking deps for selinux-policy.noarch 0-2.5.8-8.fc7 - u Checking deps for samba-common.i386 0-3.0.24-4.fc7 - None Checking deps for nash.i386 0-6.0.8-3 - u --------------------------------------------------
*** This bug has been marked as a duplicate of 420419 ***