Bug 420499 – crash in Power Manager: Just downloading some ne...

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 420499 - crash in Power Manager: Just downloading some ne...


Summary:	crash in Power Manager: Just downloading some ne...


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-20 12:21 UTC by droopy1920
Modified:	2007-03-20 21:06 UTC

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

Description droopy1920 2007-03-20 12:21:36 UTC

What were you doing when the application crashed?
Just downloading some new software with the package manager


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.2997.fc7 #1 SMP Fri Mar 16 22:29:02 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299901
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 96153600 vsize: 96153600 resident: 6144000 share: 4390912 rss: 6144000 rss_rlim: 4294967295
CPU usage: start_time: 1174377500 rtime: 6 utime: 5 stime: 1 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 -1209137440 (LWP 3020)]
(no debugging symbols found)
0x00bf3402 in __kernel_vsyscall ()

+ Trace 120326

Thread 1 (Thread -1209137440 (LWP 3020))

#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 (708 sec old) ---------------------
Checking deps for rss-glx-kde.i386 0-0.8.1.p-6.fc6 - u
Checking deps for gnucash-docs.noarch 0-2.0.1-2.fc7 - u
Checking deps for snownews.i386 0-1.5.7-5.fc6 - u
Checking deps for gwenhywfar.i386 0-2.5.4-1 - u
Checking deps for nyquist.i386 0-2.33-2.fc7 - u
Checking deps for pachi.i386 0-1.0-2.fc7 - u
Checking deps for pipenightdreams.i386 0-0.10.0-5.fc6 - u
Checking deps for libkexif.i386 0-0.2.5-1.fc7 - u
Checking deps for ufraw-common.i386 0-0.11-3.fc7 - u
Checking deps for xfce4-mailwatch-plugin.i386 0-1.0.1-5.fc7 - u
Checking deps for auriferous.i386 0-1.0.1-3.fc6 - u
Checking deps for xarchiver.i386 0-0.4.9-0.2.20070103svn24249.fc7 - u
Checking deps for offlineimap.noarch 0-4.0.16-3.fc7 - u
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-20 12:55:10 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:06:11 UTC


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