Bug 416220 – crash in Power Manager: Running updates from the...

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 416220 - crash in Power Manager: Running updates from the...


Summary:	crash in Power Manager: Running updates from the...


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-08 21:17 UTC by demiourglass
Modified:	2007-03-20 21:19 UTC

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

Description demiourglass 2007-03-08 21:17:45 UTC

What were you doing when the application crashed?
Running updates from the update manager.		


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.2975.fc7 #1 SMP Wed Mar 7 17:01:57 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: 52875264 vsize: 52875264 resident: 10698752 share: 7266304 rss: 10698752 rss_rlim: 4294967295
CPU usage: start_time: 1173385875 rtime: 127 utime: 67 stime: 60 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 -1208219936 (LWP 2511)]
(no debugging symbols found)
0x003e1402 in __kernel_vsyscall ()

+ Trace 117005

Thread 1 (Thread -1208219936 (LWP 2511))

#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 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 (1420 sec old) ---------------------
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Loading "installonlyn" plugin
/usr/sbin/pup:385: DeprecationWarning: returnSimple() will go away in a furture version of Yum.
  srpm = updating.returnSimple("sourcerpm")
/usr/sbin/pup:394: DeprecationWarning: returnSimple() will go away in a furture version of Yum.
  if updating.returnSimple("name") in rebootpkgs:
Loading "installonlyn" plugin
Loading "installonlyn" plugin
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-08 21:22:27 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:19:20 UTC


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