Bug 419255 – crash in Power Manager: Installing software, I h...

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 419255 - crash in Power Manager: Installing software, I h...


Summary:	crash in Power Manager: Installing software, I h...


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 09:06 UTC by firestone.light
Modified:	2007-03-20 21:15 UTC

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

Description firestone.light 2007-03-17 09:06:55 UTC

What were you doing when the application crashed?
Installing software, I had just updated the kernel last session.


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

System: Linux 2.6.20-1.2990.fc7 #1 SMP Thu Mar 15 19:22:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299901
Selinux: No
Accessibility: Enabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 36384768 vsize: 36384768 resident: 10813440 share: 7557120 rss: 10813440 rss_rlim: 4294967295
CPU usage: start_time: 1174120521 rtime: 20 utime: 14 stime: 6 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 -1208187168 (LWP 3385)]
(no debugging symbols found)
0x0043c402 in __kernel_vsyscall ()

+ Trace 119344

Thread 1 (Thread -1208187168 (LWP 3385))

#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 (671 sec old) ---------------------
Checking deps for gnomad2.i386 0-2.8.11-2.fc7 - u
Checking deps for libmtp.i386 0-0.1.4-1.fc7 - u
Checking deps for libid3tag.i386 0-0.15.1b-3.fc6 - u
Checking deps for mailcap.noarch 0-2.1.23-1.fc6 - u
Checking deps for gnome-user-share.i386 0-0.11-1.fc7 - u
Checking deps for libgnomeprintui22.i386 0-2.18.0-1.fc7 - u
Checking deps for apr.i386 0-1.2.8-4 - u
Checking deps for gnome-nettool.i386 0-2.18.0-1.fc7 - u
Checking deps for gtksourceview.i386 0-1.8.5-1.fc7 - u
Checking deps for audit-libs-python.i386 0-1.5-2.fc7 - u
Checking deps for urw-fonts.noarch 0-2.3-6.1.1 - u
Checking deps for gnome-mount-nautilus-properties.i386 0-0.5-3.fc7 - u
Checking deps for gnome-applet-netspeed.i386 0-0.13-7.fc6 - u
Checking deps for chkfontpath.i386 0-1.10.1-1.1 - u
warning: mailcap-2.1.23-1.fc6: Header V3 DSA signature: NOKEY, key ID 897da07a
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-17 19:43:34 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:26 UTC


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