GNOME Bugzilla – Bug 648924
crash in Bluetooth Manager: mise a niveau
Last modified: 2011-05-16 13:38:43 UTC
Version: 2.32.0 What were you doing when the application crashed? mise a niveau Distribution: Ubuntu 11.04 (natty) Gnome Release: 2.32.1 2011-04-14 (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: Glossy Icon Theme: gnome GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 31158272 vsize: 31158272 resident: 11223040 share: 8478720 rss: 11223040 rss_rlim: 18446744073709551615 CPU usage: start_time: 1304013281 rtime: 58 utime: 38 stime: 20 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/bluetooth-applet' 0x00d6c422 in __kernel_vsyscall ()
+ Trace 226935
Thread 1 (process 1747)
A debugging session is active. Inferior 1 [process 1747] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libtdb.so.1" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libltdl.so.7" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/gio/modules/libgvfsdbus.so" is not at the expected address (wrong library or version mismatch?) warning: Could not load shared library symbols for 45 libraries, e.g. /lib/libz.so.1. Use the "info sharedlibrary" command to see the complete listing. Do you need "set solib-search-path" or "set sysroot"? warning: the debug information found in "/usr/lib/debug//usr/lib/libxml2.so.2.7.8" 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.8" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 634542 ***