Bug 419303 – crash in Power Manager:

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 419303 - crash in Power Manager:


Summary:	crash in Power Manager:


Status:	RESOLVED DUPLICATE of bug 420419

Product:	gnome-power-manager
Classification:	Deprecated
Component:	gnome-power-manager
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-03-17 11:19 UTC by mkriesten
Modified:	2007-03-20 21:15 UTC

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

Description mkriesten 2007-03-17 11:19:47 UTC

What were you doing when the application crashed?



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.2967.fc7 #1 SMP Tue Mar 6 15:08:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299901
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 47890432 vsize: 47890432 resident: 6578176 share: 4935680 rss: 6578176 rss_rlim: 4294967295
CPU usage: start_time: 1174126150 rtime: 25 utime: 12 stime: 13 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 -1208912160 (LWP 2596)]
(no debugging symbols found)
0x006f9402 in __kernel_vsyscall ()

+ Trace 119380

Thread 1 (Thread -1208912160 (LWP 2596))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 g_cclosure_marshal_VOID__BOOLEAN
from /lib/libgobject-2.0.so.0
#6 g_closure_invoke
from /lib/libgobject-2.0.so.0
#7 g_cclosure_marshal_VOID__BOOLEAN
from /lib/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#9 g_signal_emit
from /lib/libgobject-2.0.so.0
#10 ??
#11 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#12 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libdbus-glib-1.so.2
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 g_cclosure_marshal_VOID__BOOLEAN
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#16 g_signal_emit
from /lib/libgobject-2.0.so.0
#17 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libdbus-glib-1.so.2
#18 dbus_connection_dispatch
from /lib/libdbus-1.so.3
#19 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libdbus-glib-1.so.2
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 g_cclosure_marshal_VOID__BOOLEAN
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 main
#0 __kernel_vsyscall





----------- .xsession-errors (4161 sec old) ---------------------
(gnome-terminal:2695): Vte-WARNING **: Can not find appropiate font for character U+ac00.
(gnome-terminal:2695): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:2695): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:2695): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:2695): Vte-WARNING **: Can not find appropiate font for character U+ac10.
GTK Accessibility Module initialized
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-17 19:43:22 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 Richard Hughes 2007-03-20 21:15:16 UTC


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