Bug 503813 – crash in Power Manager:

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 503813 - crash in Power Manager:


Summary:	crash in Power Manager:


Status:	RESOLVED DUPLICATE of bug 423795

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-12-16 04:36 UTC by umeno
Modified:	2007-12-17 22:37 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description umeno 2007-12-16 04:36:40 UTC

What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.20.2 2007-12-16 (FreeBSD GNOME Project)
BugBuddy Version: 2.20.1

System: FreeBSD 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #0: Sun Dec  9 01:23:04 JST 2007     root@belldandy.unnumbered.net:/usr/obj/usr/src/sys/ASAKURA i386
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 38004 vsize: 38004 resident: 14428 share: 38321243 rss: 14428 rss_rlim: 3607
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133

Backtrace was generated from '/usr/local/bin/gnome-power-manager'

(no debugging symbols found)...[New LWP 100193]
[Switching to LWP 100193]
0x29094659 in wait4 () from /lib/libc.so.6

+ Trace 181992

Thread 1 (LWP 100193)

#0 wait4
from /lib/libc.so.6
#1 waitpid
from /lib/libc.so.6
#2 waitpid
from /lib/libpthread.so.2
#3 g_spawn_sync
from /usr/local/lib/libglib-2.0.so.0
#4 g_spawn_command_line_sync
from /usr/local/lib/libglib-2.0.so.0
#5 bugbuddy_segv_handle
from /usr/local/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 sigaction
from /lib/libpthread.so.2
#7 <signal handler called>
#8 ??
#9 g_cclosure_marshal_VOID__BOOLEAN
from /usr/local/lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /usr/local/lib/libgobject-2.0.so.0
#11 g_signal_has_handler_pending
from /usr/local/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/local/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/local/lib/libgobject-2.0.so.0
#14 ??
#15 g_cclosure_marshal_VOID__VOID
from /usr/local/lib/libgobject-2.0.so.0
#16 dbus_g_proxy_get_type
from /usr/local/lib/libdbus-glib-1.so.2
#17 g_closure_invoke
from /usr/local/lib/libgobject-2.0.so.0
#18 g_signal_has_handler_pending
from /usr/local/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/local/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/local/lib/libgobject-2.0.so.0
#21 dbus_g_proxy_get_type
from /usr/local/lib/libdbus-glib-1.so.2
#22 dbus_connection_dispatch
from /usr/local/lib/libdbus-1.so.3
#23 dbus_g_message_get_message
from /usr/local/lib/libdbus-glib-1.so.2
#24 g_main_context_dispatch
from /usr/local/lib/libglib-2.0.so.0
#25 g_main_context_acquire
from /usr/local/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/local/lib/libglib-2.0.so.0
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 libhal_marshal_VOID__STRING_BOOLEAN_BOOLEAN_BOOLEAN
#34 ??

Output of custom script "gnome-power-bugreport.sh":
Distro version:       Kernel version:       6.3-PRERELEASE
g-p-m version:        2.20.2
HAL version:          0.5.8
System manufacturer:  missing
System version:       missing
System product:       missing
AC adapter present:   no
Battery present:      no
Laptop panel present: no
CPU scaling present:  no
Battery Information:
GNOME Power Manager Process Information:
HAL Process Information:

Comment 1 Susana 2007-12-17 22:37:45 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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