Bug 491387 – crash in Battery Charge Monitor: suspending/resuming 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 491387 - crash in Battery Charge Monitor: suspending/resuming the ...


Summary:	crash in Battery Charge Monitor: suspending/resuming the ...


Status:	RESOLVED DUPLICATE of bug 456028

Product:	gnome-applets
Classification:	Other
Component:	battery
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-applets Maintainers
QA Contact:	gnome-applets Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-29 14:05 UTC by glenn.story
Modified:	2007-10-30 11:29 UTC

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

Description glenn.story 2007-10-29 14:05:39 UTC

What were you doing when the application crashed?
suspending/resuming the machine




			




Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1.emp3 #1 SMP PREEMPT Wed Oct 17 18:26:16 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 26230784 vsize: 26230784 resident: 9265152 share: 7356416 rss: 9265152 rss_rlim: 4294967295
CPU usage: start_time: 1193631094 rtime: 63 utime: 55 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/battstat-applet-2'

(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 -1208539424 (LWP 5063)]
(no debugging symbols found)
0xb7fa1410 in __kernel_vsyscall ()

+ Trace 173676

Thread 1 (Thread -1208539424 (LWP 5063))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_str_hash
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_str_hash
from /lib/libdbus-1.so.3
#8 g_str_hash
from /lib/libdbus-1.so.3
#9 dbus_move_error
from /lib/libdbus-1.so.3
#10 libhal_device_property_exists
from /usr/lib/libhal.so.1
#11 ??
#12 g_str_hash
from /usr/lib/libhal.so.1
#13 dbus_connection_dispatch
from /lib/libdbus-1.so.3
#14 g_str_hash
from /usr/lib/libdbus-glib-1.so.2
#15 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#16 g_str_hash
from /lib/libglib-2.0.so.0
#17 g_main_loop_run
from /lib/libglib-2.0.so.0
#18 bonobo_main
from /usr/lib/libbonobo-2.so.0
#19 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#20 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#21 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#22 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#23 main
#0 __kernel_vsyscall



----------- .xsession-errors (910 sec old) ---------------------
(gnome-panel:5015): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
** Message: <info>  You are now connected to the wired network.
** Message: <info>  You are now connected to the wireless network 'storyhome'.
** (gnome-help:14595): WARNING **: failure: no device event controller found.
** (gnome-help:14595): WARNING **: failure: no device event controller found.
** (gnome-help:14595): WARNING **: failure: no device event controller found.
--------------------------------------------------

Comment 1 palfrey 2007-10-30 11:29:07 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

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