Bug 597462 – crash in Battery Charge Monitor: I tried to plug iPod.

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 597462 - crash in Battery Charge Monitor: I tried to plug iPod.


Summary:	crash in Battery Charge Monitor: I tried to plug iPod.


Status:	RESOLVED DUPLICATE of bug 446097

Product:	gnome-applets
Classification:	Other
Component:	battery
Version:	unspecified
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	gnome-applets Maintainers
QA Contact:	gnome-applets Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-10-05 19:12 UTC by Łukasz Wojciech Hebda
Modified:	2009-10-05 22:53 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description Łukasz Wojciech Hebda 2009-10-05 19:12:14 UTC

What were you doing when the application crashed?
I tried to plug iPod.


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.24.3 2009-06-02 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.27-gentoo-r8 #5 Thu Jul 9 01:11:27 CEST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SmoothGNOME-Green
Icon Theme: SmoothGNOME

Memory status: size: 26419200 vsize: 26419200 resident: 11706368 share: 10137600 rss: 11706368 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254769714 rtime: 8 utime: 8 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/battstat-applet-2'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6cc1750 (LWP 6096)]
0xb7f23424 in __kernel_vsyscall ()

+ Trace 218072

Thread 1 (Thread 0xb6cc1750 (LWP 6096))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at gspawn.c line 694
#4 run_bug_buddy
at gnome-breakpad.cc line 223
#5 check_if_gdb
at gnome-breakpad.cc line 292
#6 bugbuddy_segv_handle
at gnome-breakpad.cc line 84
#7 <signal handler called>
#8 __kernel_vsyscall
#9 *__GI_raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
#10 *__GI_abort
at abort.c line 88
#11 _dbus_abort
at dbus-sysdeps.c line 86
#12 _dbus_warn_check_failed
#13 dbus_move_error
at dbus-errors.c line 278
#14 libhal_device_property_exists
at libhal.c line 2690
#15 device_added_callback
at battstat-hal.c line 311
#16 filter_func
at libhal.c line 1053
#17 dbus_connection_dispatch
at dbus-connection.c line 4406
#18 message_queue_dispatch
at dbus-gmain.c line 101
#19 IA__g_main_context_dispatch
at gmain.c line 2144
#20 g_main_context_iterate
at gmain.c line 2778
#21 IA__g_main_loop_run
at gmain.c line 2986
#22 bonobo_main
at bonobo-main.c line 311
#23 bonobo_generic_factory_main_timeout
at bonobo-generic-factory.c line 411
#24 bonobo_generic_factory_main
at bonobo-generic-factory.c line 368
#25 panel_applet_factory_main_closure
at panel-applet.c line 1754
#26 panel_applet_factory_main
at panel-applet.c line 1778
#27 main
at battstat_applet.c line 1685
#0 __kernel_vsyscall



----------- .xsession-errors (137 sec old) ---------------------
(emacs:6168): Gtk-WARNING **: Kan themamodule in modulepad: ‘smooth’ niet vinden,
(emacs:6168): Gtk-WARNING **: Kan themamodule in modulepad: ‘smooth’ niet vinden,
(emacs:6168): Gtk-WARNING **: Kan themamodule in modulepad: ‘smooth’ niet vinden,
(emacs:6168): Gtk-WARNING **: Kan themamodule in modulepad: ‘smooth’ niet vinden,
(emacs:6168): Gtk-WARNING **: Kan themamodule in modulepad: ‘smooth’ niet vinden,
(emacs:6168): Gtk-WARNING **: Kan themamodule in modulepad: ‘smooth’ niet vinden,
(gnome-terminal:6165): Vte-WARNING **: DECSET/DECRESET mode 1034 not recognized, ignoring.
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-10-05 22:53:01 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 bug 446097 ***