Bug 478517 – crash in Battery Charge Monitor:

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 478517 - crash in Battery Charge Monitor:


Summary:	crash in Battery Charge Monitor:


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-09-20 08:57 UTC by lmj226
Modified:	2007-10-06 09:46 UTC

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

Description lmj226 2007-09-20 08:57:09 UTC

What were you doing when the application crashed?



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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 49451008 vsize: 49451008 resident: 12939264 share: 9613312 rss: 12939264 rss_rlim: 4294967295
CPU usage: start_time: 1190255014 rtime: 10 utime: 8 stime: 2 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 -1209063712 (LWP 2971)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 164074

Thread 1 (Thread -1209063712 (LWP 2971))

#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 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 ??
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 (388 sec old) ---------------------
	libpthread.so.0 => /lib/libpthread.so.0 (0x00309000)
	libstlport_gcc.so => /usr/lib/openoffice.org/program/libstlport_gcc.so (0x00321000)
	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x003e2000)
	libm.so.6 => /lib/libm.so.6 (0x004cd000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x004f6000)
	libc.so.6 => /lib/libc.so.6 (0x00502000)
	libcrypt.so.1 => /lib/libcrypt.so.1 (0x00656000)
	/lib/ld-linux.so.2 (0x80000000)
...end sample ldd details ...
---end copy and paste here---
paste the above into your bug report
窗口管理器警告：Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x100005b (OpenOffice)
窗口管理器警告：meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
窗口管理器警告：Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1000106 (Ajax - Ope)
窗口管理器警告：meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Susana 2007-10-06 09:46:13 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 ***