Bug 507313 – crash in Battery Charge Monitor: vmware-config.pl

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 507313 - crash in Battery Charge Monitor: vmware-config.pl


Summary:	crash in Battery Charge Monitor: vmware-config.pl


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:	2008-01-04 18:18 UTC by goths
Modified:	2008-02-11 09:56 UTC

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

Description goths 2008-01-04 18:18:17 UTC

What were you doing when the application crashed?
vmware-config.pl




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

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 253739008 vsize: 253739008 resident: 7749632 share: 6328320 rss: 7749632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199470530 rtime: 2 utime: 1 stime: 1 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496359152 (LWP 6168)]
(no debugging symbols found)
0x0000003edc60d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 184080

Thread 1 (Thread 46912496359152 (LWP 6168))

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

Comment 1 Cosimo Cecchi 2008-02-11 09:56:23 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 446097 ***