Bug 515644 – crash in Battery Charge Monitor: pulled out USB stick

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 515644 - crash in Battery Charge Monitor: pulled out USB stick


Summary:	crash in Battery Charge Monitor: pulled out USB stick


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-10 22:04 UTC by A.M.Rucklidge
Modified:	2008-02-10 23:39 UTC

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

Description A.M.Rucklidge 2008-02-10 22:04:32 UTC

What were you doing when the application crashed?
pulled out USB stick



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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 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: 25370624 vsize: 25370624 resident: 4288512 share: 2420736 rss: 4288512 rss_rlim: 4294967295
CPU usage: start_time: 1201984942 rtime: 369 utime: 301 stime: 68 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 1073921664 (LWP 2955)]
(no debugging symbols found)
0x40000402 in __kernel_vsyscall ()

+ Trace 188764

Thread 1 (Thread 1073921664 (LWP 2955))

#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 (136309 sec old) ---------------------
                 System error: Input/output error
scsi_read error: sector=313503 length=24 retry=0
                 Sense key: 3 ASC: 11 ASCQ: 5
                 Transport error: Medium reading data from medium
                 System error: Input/output error
scsi_read error: sector=313503 length=12 retry=1
                 Sense key: 3 ASC: 11 ASCQ: 5
                 Transport error: Medium reading data from medium
                 System error: Input/output error
scsi_read error: sector=313503 length=6 retry=2
                 Sense key: 3 ASC: 11 ASCQ: 5
                 Transport error: Medium reading data from medium
                 System error: Input/output error
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Gianluca Borello 2008-02-10 23:39:31 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 ***