Bug 491414 – crash in Battery Charge Monitor: Suspend/resume

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 491414 - crash in Battery Charge Monitor: Suspend/resume


Summary:	crash in Battery Charge Monitor: Suspend/resume


Status:	RESOLVED DUPLICATE of bug 472014

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 15:23 UTC by Christopher Beland
Modified:	2007-10-30 11:29 UTC

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

Description Christopher Beland 2007-10-29 15:23:30 UTC

What were you doing when the application crashed?
Suspend/resume


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

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 41103360 vsize: 41103360 resident: 19247104 share: 16072704 rss: 19247104 rss_rlim: 4294967295
CPU usage: start_time: 1193525655 rtime: 72 utime: 62 stime: 10 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 -1209104672 (LWP 2275)]
0x00110402 in __kernel_vsyscall ()

+ Trace 173696

Thread 1 (Thread -1209104672 (LWP 2275))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
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 ??
from /lib/libdbus-1.so.3
#8 ??
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 ??
from /usr/lib/libhal.so.1
#13 dbus_connection_dispatch
from /lib/libdbus-1.so.3
#14 ??
from /usr/lib/libdbus-glib-1.so.2
#15 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#16 ??
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 (10 sec old) ---------------------
(evolution:7320): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7320): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7320): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7320): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7320): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7320): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:7320): camel-WARNING **: camel_exception_get_id called with NULL parameter.
** Message: <info>  You are now connected to the wired network.
--------------------------------------------------

Comment 1 palfrey 2007-10-30 11:29:19 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 472014 ***