Bug 489299 – crash in Battery Charge Monitor: coming out of suspend

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 489299 - crash in Battery Charge Monitor: coming out of suspend


Summary:	crash in Battery Charge Monitor: coming out of suspend


Status:	RESOLVED DUPLICATE of bug 446097

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-23 08:27 UTC by bryan.anderson
Modified:	2007-10-28 16:36 UTC

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

Description bryan.anderson 2007-10-23 08:27:30 UTC

What were you doing when the application crashed?
coming out of suspend


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.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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 36757504 vsize: 36757504 resident: 18194432 share: 15642624 rss: 18194432 rss_rlim: 4294967295
CPU usage: start_time: 1193098997 rtime: 43 utime: 35 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 -1209145632 (LWP 3145)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 172149

Thread 1 (Thread -1209145632 (LWP 3145))

#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 (60 sec old) ---------------------
      1338 | 19.03.2006 22:46:08 | skin/sliderhor.bmp
      2170 | 12.03.2006 09:17:26 | skin/sliderver.bmp
      3382 | 12.03.2006 09:17:26 | skin/tomtom.bmp
      4726 | 28.06.2006 23:53:16 | sdkregistry/nmealogger.bmp
       158 | 20.08.2006 17:04:04 | sdkregistry/nmealogger.cap
All done, no errors.
/scratch/Xilinx91i/bin/lin:/usr/local/xhdl/bin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin
WARNING:ProjectMgmt - "/scratch/VHDL/emerl_final/adc8/adc8/adc8_2/adc8.ngr" line
   0 duplicate design unit: 'Module|adc8'
WARNING:ProjectMgmt - "/scratch/VHDL/emerl_final/adc8/adc8/adc8_2/adc8_map.ncd"
   line 0 duplicate design unit: 'Module|adc8'
** Message: <info>  You are now connected to the wired network.
--------------------------------------------------

Comment 1 André Klapper 2007-10-28 16:36:00 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 446097 ***