GNOME Bugzilla – Bug 414323
crash in Power Statistics: Package updater was runn...
Last modified: 2007-03-04 12:05:49 UTC
What were you doing when the application crashed? Package updater was running (downloading files) and I just opened Power History to see what it did. I was looking at graph type drop down menu when it crashed. Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.91 2007-02-13 (Red Hat, Inc) BugBuddy Version: 2.17.3 System: Linux 2.6.20-1.2949.fc7 #1 SMP Mon Feb 26 18:37:35 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: Enforcing Accessibility: Enabled Memory status: size: 52178944 vsize: 0 resident: 52178944 share: 0 rss: 12435456 rss_rlim: 0 CPU usage: start_time: 1172902869 rtime: 0 utime: 41 stime: 0 cutime:29 cstime: 0 timeout: 12 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-power-statistics' (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 -1208641824 (LWP 2911)] (no debugging symbols found) 0x003f2402 in __kernel_vsyscall ()
+ Trace 115532
Thread 1 (Thread -1208641824 (LWP 2911))
----------- .xsession-errors --------------------- Checking deps for openoffice.org-xsltfilter.i386 1-2.2.0-8.1 - None Checking deps for libgnomeprintui22.i386 0-2.17.91-1.fc7 - None Checking deps for audit-libs.i386 0-1.4.2-1.fc7 - None Checking deps for e2fsprogs-libs.i386 0-1.39-11 - u Checking deps for neon-devel.i386 0-0.25.5-5.1 - None Checking deps for nautilus-cd-burner.i386 0-2.17.7-1.fc7 - None Checking deps for libbonoboui-devel.i386 0-2.17.94-1.fc7 - u Checking deps for gnome-python2-gtkhtml2.i386 0-2.14.2-9.fc7 - None Checking deps for libsysfs.i386 0-2.1.0-1.fc7 - u GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
*** This bug has been marked as a duplicate of 414275 ***