Bug 421635 – crash in Power Manager: I was in the kitchen eat...

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 421635 - crash in Power Manager: I was in the kitchen eat...


Summary:	crash in Power Manager: I was in the kitchen eat...


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-22 20:39 UTC by russ
Modified:	2007-03-23 22:39 UTC

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

Description russ 2007-03-22 20:39:48 UTC

What were you doing when the application crashed?
I was in the kitchen eating lunch


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

System: Linux 2.6.20.3 #3 Thu Mar 22 14:02:08 MDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 66736128 vsize: 66736128 resident: 9310208 share: 6270976 rss: 9310208 rss_rlim: 4294967295
CPU usage: start_time: 1174594043 rtime: 21 utime: 21 stime: 0 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 -1228642592 (LWP 3033)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 121257

Thread 1 (Thread -1228642592 (LWP 3033))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__BOOLEAN
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 ---------------------
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory
position: 0 0 1600 1200
effective alpha: 255
free
You can not run beagle as root.  Beagle is designed to run from your own
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.
end from FAM server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-23 22:39:14 UTC


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