GNOME Bugzilla – Bug 628751
crash in Bluetooth Manager:
Last modified: 2010-10-04 09:36:36 UTC
Version: 2.30.0 What were you doing when the application crashed? Distribution: Ubuntu 10.10 (maverick) Gnome Release: 2.31.90 2010-08-18 (Ubuntu) BugBuddy Version: 2.31.3 System: Linux 2.6.35-020635-generic #020635 SMP Mon Aug 2 09:08:21 UTC 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10706000 Selinux: No Accessibility: Disabled GTK+ Theme: Amaranth Icon Theme: Gorilla GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 225226752 vsize: 225226752 resident: 11911168 share: 8712192 rss: 11911168 rss_rlim: 18446744073709551615 CPU usage: start_time: 1283495110 rtime: 163 utime: 135 stime: 28 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] 0x00007fbbfff7369e in waitpid () from /lib/libpthread.so.0
+ Trace 223546
Thread 1 (Thread 0x7fbc037938e0 (LWP 2510))
A debugging session is active. Inferior 1 [process 2510] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** Gtk **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed ----------- .xsession-errors --------------------- (<unknown>:13207): Gdk-CRITICAL **: IA__gdk_pixbuf_get_from_drawable: assertion `src_x >= 0 && src_y >= 0' failed (<unknown>:13207): Gdk-CRITICAL **: IA__gdk_pixbuf_get_from_drawable: assertion `src_x >= 0 && src_y >= 0' failed (<unknown>:13207): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (<unknown>:13207): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed warning: .dynamic section for "/usr/lib/libgio-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgobject-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib/libglib-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib/libc.so.6" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
only glib related traces 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!
Unable to crash the programm again, bug appeared suddenly out of nothing. I did not use Bluetooth since I installed 10.10.
I want to mention that the gmome-bluetooth-manager is not working anymore since this crash. there were no problems before, but now I can not connect to my mobile phone anymore. unfortunately I have no other bluetooth device to try a different one.
(In reply to comment #3) > I want to mention that the gmome-bluetooth-manager is not working anymore since > this crash. there were no problems before, but now I can not connect to my > mobile phone anymore. unfortunately I have no other bluetooth device to try a > different one. What does "not working" actually mean? If you can't connect to your phone, there's probably another bug somewhere. Check /var/log/messages for messages from bluetoothd and the kernel.
I see the little icon in my status bar, but when i try to connect to the phone, send data to the phone or recieve data from the phone nothing happens, not even an error-message. My computer is set to "visible" in the gnome-bluetooth-manager and because I had a connection to my phone once the computer can be found, but I can not establish a connection, the phone states: "out of range" in the /var/log/messages I can not find anything from the gnome-bluetooth-manager.
I just checked my devices. I wondered if the Bluetooth device is seen in "lspci" but the device is gone without a trace... I will try to fix that and comment on the outcome! If I am wrong with the assumption that the bluetooth device should be in "lspci" please tell me so.
Created attachment 169767 [details] bluetooth-applet terminal errors
(In reply to comment #6) > I just checked my devices. I wondered if the Bluetooth device is seen in > "lspci" but the device is gone without a trace... > > I will try to fix that and comment on the outcome! > If I am wrong with the assumption that the bluetooth device should be in > "lspci" please tell me so. I think I found the source of the problem: I am using an ASUS G1s Maschine, with the option "Fn+F2" 1st press: bluetooth+wifi on 2nd press: bluetooth off + wifi on 3rd press: bluetooth+wifi off 4th press: bluetooth on + wifi off attached please find the terminal output of bluetooth-applet when pressing the combination 4 times. as comment i use "//<text>"
(In reply to comment #6) > I just checked my devices. I wondered if the Bluetooth device is seen in > "lspci" but the device is gone without a trace... It would usually be in lsusb instead.
All the errors listed are either fixed in newer versions of gnome-bluetooth, or Ubuntu specific errors. File a bug against Ubuntu for those, and we'll see whether the problem still exists after that.
The OP sent an email to the ubuntu-bugsquad ML [1] where he states there are no problems after upgrades. @Bastien: I do not know how you want to close this bug, so I leave it to you. [1] https://lists.ubuntu.com/archives/ubuntu-bugsquad/2010-October/002719.html
Closing as obsolete then.