Bug 515352 – crash in Battery Charge Monitor: I plugged my BlackBerry'...

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 515352 - crash in Battery Charge Monitor: I plugged my BlackBerry'...


Summary:	crash in Battery Charge Monitor: I plugged my BlackBerry'...


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-02-09 06:18 UTC by linuxvis
Modified:	2008-02-09 18:40 UTC

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

Description linuxvis 2008-02-09 06:18:46 UTC

What were you doing when the application crashed?
I plugged my BlackBerry's USB cable into my laptop in order to charge the battery.  A while back, I installed these packages, which contains a program to increase the current on the USB port from 100mA to 500mA:
barry-gui-0.11-1
libbarry-0.11-1
barry-opensync-0.11-1
barry-util-0.11-1



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 21:18:02 EST 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: 23908352 vsize: 23908352 resident: 8433664 share: 7286784 rss: 8433664 rss_rlim: 4294967295
CPU usage: start_time: 1202500537 rtime: 43 utime: 36 stime: 7 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 -1208363296 (LWP 3195)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 188616

Thread 1 (Thread -1208363296 (LWP 3195))

#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

Comment 1 Gianluca Borello 2008-02-09 18:40:47 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 ***