GNOME Bugzilla – Bug 412345
crash in Power Statistics: crashed on startup
Last modified: 2007-05-03 21:15:24 UTC
What were you doing when the application crashed? crashed on startup 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.2947.fc7 #1 SMP Sun Feb 25 19:09:44 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: Enforcing Accessibility: Enabled Memory status: size: 52195328 vsize: 0 resident: 52195328 share: 0 rss: 12390400 rss_rlim: 0 CPU usage: start_time: 1172515397 rtime: 0 utime: 18 stime: 0 cutime:13 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-power-statistics' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208674592 (LWP 3090)] 0x00f3e402 in __kernel_vsyscall ()
+ Trace 114099
Thread 1 (Thread -1208674592 (LWP 3090))
----------- .xsession-errors --------------------- (gnome-terminal:3019): Vte-WARNING **: Can not find appropiate font for character U+7a0b. (gnome-terminal:3019): Vte-WARNING **: Can not find appropiate font for character U+5f0f. GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Cannot access memory at address 0x1 Cannot access memory at address 0x1 --------------------------------------------------
Hmm. I can't see an obvious bug in the code - could you try adding some more debuginfo packages and see if you can reproduce. Thanks.
Sure, no problem. Note that it doesn't happen *right* on startup - it's about 15 seconds after startup (with no user interaction). Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.92 2007-02-27 (Red Hat, Inc) BugBuddy Version: 2.17.4 System: Linux 2.6.20-1.2953.fc7 #1 SMP Mon Feb 26 21:12:04 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: Permissive Accessibility: Enabled GTK+ Theme: Bluecurve Icon Theme: Echo Memory status: size: 288931840 vsize: 288931840 resident: 14692352 share: 10465280 rss: 14692352 rss_rlim: 18446744073709551615 CPU usage: start_time: 1172690756 rtime: 16 utime: 10 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-power-statistics' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912676844800 (LWP 3932)] 0x00002aaab00ea805 in waitpid () from /lib64/libpthread.so.0
+ Trace 114704
Thread 1 (Thread 46912676844800 (LWP 3932))
----------- .xsession-errors (81 sec old) --------------------- Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized 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 is with: gnome-power-manager-2.17.92 gtk2-2.10.9 cairo-1.3.14 glib2-2.12.9 libgnomecanvas-2.14.0
I'll work on this today.
*** Bug 413927 has been marked as a duplicate of this bug. ***
*** Bug 414075 has been marked as a duplicate of this bug. ***
*** Bug 414112 has been marked as a duplicate of this bug. ***
*** Bug 414196 has been marked as a duplicate of this bug. ***
2007-03-04 Richard Hughes <richard@hughsie.com> * src/gpm-graph-widget.c: (gpm_graph_widget_draw_line): * src/gpm-statistics-core.c: (gpm_statistics_graph_refresh): Fix the segfault when we try to draw a graph that does not exist. Fixes #412345 and plenty more duplicates.
*** Bug 414687 has been marked as a duplicate of this bug. ***
*** Bug 414833 has been marked as a duplicate of this bug. ***
*** Bug 414871 has been marked as a duplicate of this bug. ***
*** Bug 415241 has been marked as a duplicate of this bug. ***
*** Bug 415568 has been marked as a duplicate of this bug. ***
*** Bug 416019 has been marked as a duplicate of this bug. ***
*** Bug 416051 has been marked as a duplicate of this bug. ***
*** Bug 416401 has been marked as a duplicate of this bug. ***
*** Bug 415994 has been marked as a duplicate of this bug. ***
*** Bug 417299 has been marked as a duplicate of this bug. ***
*** Bug 417738 has been marked as a duplicate of this bug. ***
*** Bug 418420 has been marked as a duplicate of this bug. ***
*** Bug 434214 has been marked as a duplicate of this bug. ***
*** Bug 429625 has been marked as a duplicate of this bug. ***
*** Bug 435638 has been marked as a duplicate of this bug. ***
Hmm I got the crash with 2.19.1