Bug 434214 – crash in Power Statistics: Moving the window of pow...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 434214 - crash in Power Statistics: Moving the window of pow...


Summary:	crash in Power Statistics: Moving the window of pow...


Status:	RESOLVED DUPLICATE of bug 412345

Product:	gnome-power-manager
Classification:	Deprecated
Component:	gnome-power-statistics
Version:	2.17.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Power Manager Maintainer(s)
QA Contact:	GNOME Power Manager Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-28 21:33 UTC by danielpa
Modified:	2007-04-29 11:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Attachments
Backtrace with debug symbols (20.32 KB, text/plain) 2007-04-29 08:34 UTC, danielpa	Details

Description danielpa 2007-04-28 21:33:58 UTC

What were you doing when the application crashed?
Moving the window of power history


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:36:44 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Yattacier3
Icon Theme: Yattacier3

Memory status: size: 37388288 vsize: 37388288 resident: 12369920 share: 9641984 rss: 12369920 rss_rlim: 4294967295
CPU usage: start_time: 1177795890 rtime: 17 utime: 13 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 -1208211744 (LWP 3944)]
(no debugging symbols found)
0x005e7402 in __kernel_vsyscall ()

+ Trace 131161

Thread 1 (Thread -1208211744 (LWP 3944))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 ??
from /usr/lib/libgtk-x11-2.0.so.0
#6 ??
from /lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /lib/libgobject-2.0.so.0
#8 ??
from /lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#10 g_signal_emit
from /lib/libgobject-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgdk-x11-2.0.so.0
#14 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 main
#0 __kernel_vsyscall



----------- .xsession-errors (101 sec old) ---------------------
(gnome-terminal:3602): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:3602): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:3602): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:3602): Vte-WARNING **: Can not find appropiate font for character U+ac10.
(gnome-terminal:3602): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
** Message: Found best visual for GL: 0x25
--------------------------------------------------

Comment 1 palfrey 2007-04-28 22:55:38 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 danielpa 2007-04-29 08:34:29 UTC

Created attachment 87224 [details]
Backtrace with debug symbols

Comment 3 danielpa 2007-04-29 08:36:21 UTC

I've added debug support to gnome-power-statistics, gtk+, gnome-vfs and gnome-applets, I hope that the following trace helps. I forgot to mention that I'm running a Fedora 7 Test 4 (almost stable) and this bug could be just related to Fedora/Redhat distribution and not to gnome-power-statistics current stream of development.

I'd like to add that I can reproduce this bug without any interaction at all with gnome-power-statistics (I reported that I was [accidentally] moving the window).

Comment 4 palfrey 2007-04-29 11:01:11 UTC

Thanks for the improved trace. It looks like this is a duplicate of Bug 412345, which has now been fixed in the subversion version of gnome-power-manager, and should be in the next release. Thanks for your time!

*** This bug has been marked as a duplicate of 412345 ***