Bug 414604 – crash in Power Manager: new install

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 414604 - crash in Power Manager: new install


Summary:	crash in Power Manager: new install


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-04 15:14 UTC by ceb7
Modified:	2007-03-20 21:20 UTC

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

Description ceb7 2007-03-04 15:14:34 UTC

What were you doing when the application crashed?
new install


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.2962.fc7 #1 SMP Fri Mar 2 19:00:23 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 288927744 vsize: 288927744 resident: 11997184 share: 7327744 rss: 11997184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1173020475 rtime: 9 utime: 6 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912681117120 (LWP 3953)]
(no debugging symbols found)
0x00002aaab0923805 in waitpid () from /lib64/libpthread.so.0

+ Trace 115759

Thread 1 (Thread 46912681117120 (LWP 3953))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#5 g_cclosure_marshal_VOID__BOOLEAN
from /lib64/libgobject-2.0.so.0
#6 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#7 g_signal_emit
from /lib64/libgobject-2.0.so.0
#8 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib64/libdbus-glib-1.so.2
#9 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#10 g_cclosure_marshal_VOID__BOOLEAN
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit
from /lib64/libgobject-2.0.so.0
#13 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib64/libdbus-glib-1.so.2
#14 dbus_connection_dispatch
from /lib64/libdbus-1.so.3
#15 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib64/libdbus-glib-1.so.2
#16 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#17 g_cclosure_marshal_VOID__BOOLEAN
from /lib64/libglib-2.0.so.0
#18 g_main_loop_run
from /lib64/libglib-2.0.so.0
#19 main
#0 waitpid
from /lib64/libpthread.so.0
#6 <signal handler called>
#7 mono_class_vtable
#8 mono_array_new_full
#9 ??
#10 ??
#11 ??
#0 fork
from /lib64/libc.so.6

Comment 1 Richard Hughes 2007-03-04 15:36:14 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:20:38 UTC


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