GNOME Bugzilla – Bug 632822
crash in Bluetooth Manager: updating
Last modified: 2010-10-22 12:32:50 UTC
Version: 2.32.0 What were you doing when the application crashed? updating Distribution: Ubuntu 10.10 (maverick) Gnome Release: 2.32.0 2010-09-27 (Ubuntu) BugBuddy Version: 2.31.92 System: Linux 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10900000 Selinux: No Accessibility: Disabled GTK+ Theme: Human-Clearlooks Icon Theme: Humanity GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 76095488 vsize: 76095488 resident: 10723328 share: 8667136 rss: 10723328 rss_rlim: 18446744073709551615 CPU usage: start_time: 1287688949 rtime: 9 utime: 7 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/bluetooth-applet' [Thread debugging using libthread_db enabled] [New Thread 0xb768bb70 (LWP 1631)] 0x00376422 in __kernel_vsyscall ()
+ Trace 224268
Thread 1 (Thread 0xb788c820 (LWP 1624))
A debugging session is active. Inferior 1 [process 1624] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- warning: the debug information found in "/usr/lib/debug//usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). --------------------------------------------------
GTK+ doesn't seem to like it when the icon cache changes underneath it.
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 614800 ***