Bug 414763 – crash in Power Manager: nothing.

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 414763 - crash in Power Manager: nothing.


Summary:	crash in Power Manager: nothing.


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-05 01:57 UTC by bcwise
Modified:	2007-03-20 21:20 UTC

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

Description bcwise 2007-03-05 01:57:32 UTC

What were you doing when the application crashed?
nothing.


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:18:31 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 71098368 vsize: 71098368 resident: 10551296 share: 7118848 rss: 10551296 rss_rlim: 4294967295
CPU usage: start_time: 1173052913 rtime: 24 utime: 16 stime: 8 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 -1208432928 (LWP 3909)]
(no debugging symbols found)
0x002d1402 in __kernel_vsyscall ()

+ Trace 115893

Thread 1 (Thread -1208432928 (LWP 3909))

#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 g_cclosure_marshal_VOID__BOOLEAN
from /lib/libgobject-2.0.so.0
#6 g_closure_invoke
from /lib/libgobject-2.0.so.0
#7 ??
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 ??
from /usr/lib/libdbus-glib-1.so.2
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 ??
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 ??
from /usr/lib/libdbus-glib-1.so.2
#18 dbus_connection_dispatch
from /lib/libdbus-1.so.3
#19 ??
from /usr/lib/libdbus-glib-1.so.2
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 ??
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 (6411 sec old) ---------------------
  import gimp
/usr/lib/gimp/2.0/plug-ins/py-slice.py:22: RuntimeWarning: Python C API version mismatch for module gimp: This Python has API version 1013, module gimp has version 1012.
  import gimp
/usr/lib/gimp/2.0/python/gimpfu.py:65: RuntimeWarning: Python C API version mismatch for module gimp: This Python has API version 1013, module gimp has version 1012.
  import gimp
MPlayer 1.0rc1-4.1.2 (C) 2000-2006 MPlayer Team
CPU: Intel(R) Pentium(R) M processor 1.73GHz (Family: 6, Model: 13, Stepping: 8)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled for x86 CPU with extensions: MMX MMX2 SSE SSE2
GTK Accessibility Module initialized
Window manager warning: Window 0x540000b (MPlayer) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 448 x 170; this doesn't make much sense.
Exiting... (Exit)
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-05 08:40:48 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 bcwise 2007-03-05 13:47:34 UTC

Richard, I did as you suggested and installed the debugging package for gnome-power-manager and I also installed the debugging packages for glib2, gtk2 and gnome-vfs2.
  This morning when I logged in to my machine the system downloaded and installed some updates. I have not seen the problem happening now. The power manager seems to be working properly now but if it occurs again I will definitely send you the stack trace. Thanks.

Carlo Wise

Comment 3 Richard Hughes 2007-03-20 21:20:18 UTC


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