GNOME Bugzilla – Bug 566789
crash in Battery Charge Monitor: I was plugging an USB st...
Last modified: 2009-01-07 15:26:24 UTC
What were you doing when the application crashed? I was plugging an USB storage on a USB switch. Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.22.3 2008-08-21 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.27-gentoo-r7 #4 SMP Fri Jan 2 18:35:06 CET 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 25890816 vsize: 25890816 resident: 11591680 share: 9850880 rss: 11591680 rss_rlim: 4294967295 CPU usage: start_time: 1231257536 rtime: 20 utime: 16 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/battstat-applet-2' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6c1e6e0 (LWP 7156)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 211318
Thread 1 (Thread 0xb6c1e6e0 (LWP 7156))
----------- .xsession-errors (20 sec old) --------------------- Bonobo-Activation-Message: About to register 'OAFIID:Nautilus_Shell': 0x81a8380 Bonobo-Activation-Message: Registration environment for 'DISPLAY' = ':0.0' Bonobo-Activation-Message: registration of 'OAFIID:Nautilus_Shell' returns (already active) Bonobo-Activation-Message: Successfully registered `OAFIID:Nautilus_Shell' ** (nautilus:10380): WARNING **: FIXME: Need to shutdown linc connections ... Bonobo-Activation-Message: Reset cache Bonobo-Activation-Message: Reset cache Bonobo-Activation-Message: Reset cache Bonobo-Activation-Message: Reset cache gnome-mount 0.6 Mounted /dev/sda1 at "/media/disk" ** (gnome-mount:10596): WARNING **: FIXME: Need to shutdown linc connections ... --------------------------------------------------
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 ***