GNOME Bugzilla – Bug 751863
bluetooth configuration panel is blank, can't configure anything
Last modified: 2015-07-08 02:55:25 UTC
Created attachment 306664 [details] screenshot of problem Description of problem: Version-Release number of selected component (if applicable): control-center-3.16.2-1.fc22.x86_64 NetworkManager-bluetooth-1.0.4-0.1.git20160624.f245b49a.fc22.x86_64 bluez-libs-5.29-2.fc22.x86_64 bluez-5.29-2.fc22.x86_64 pulseaudio-module-bluetooth-6.0-4.fc22.x86_64 gnome-bluetooth-libs-3.16.1-1.fc22.x86_64 gnome-bluetooth-3.16.1-1.fc22.x86_64 bluez-cups-5.29-2.fc22.x86_64 How reproducible: Always Steps to Reproduce: 1. Open control center, click on Bluetooth icon 2. 3. Actual results: Blank, see screenshot Expected results: I should be able to do something in here, like browse for bluetooth devices and configure them to use with GNOME. Additional info: When I first enter the panel, it's completely blank, unlike the attached screen shot. As soon as I click another window (Terminal, to take the screen shot), then the words "Devices" and "Visible as "Foobar"" appear, but I still can't do anything in here at all.
What's the output of: rfkill list and: hciconfig ?
[root@f22m chris]# rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no [root@f22m chris]# hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:6 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0
Created attachment 306672 [details] journal journalctl -b -l -o short-monotonic
[root@f22m chris]# systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2015-07-02 16:46:50 MDT; 5min ago Docs: man:bluetoothd(8) Main PID: 812 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─812 /usr/libexec/bluetooth/bluetoothd Jul 02 16:46:50 f22m.localdomain systemd[1]: Starting Bluetooth service... Jul 02 16:46:50 f22m.localdomain bluetoothd[812]: Bluetooth daemon 5.29 Jul 02 16:46:50 f22m.localdomain bluetoothd[812]: Starting SDP server Jul 02 16:46:50 f22m.localdomain bluetoothd[812]: Bluetooth management interface 1.9 initialized Jul 02 16:46:50 f22m.localdomain systemd[1]: Started Bluetooth service.
Created attachment 306673 [details] lspci
(In reply to Chris Murphy from comment #2) > [root@f22m chris]# hciconfig > hci0: Type: BR/EDR Bus: USB > BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 > DOWN > RX bytes:6 acl:0 sco:0 events:1 errors:0 > TX bytes:3 acl:0 sco:0 commands:1 errors:0 The adapter is down, but present. The Bluetooth panel will try to force it "up" when you start it, but that somehow doesn't happen. What's the output of: gdbus introspect --system --dest org.bluez --object-path /org/bluez/hci0 before launching the panel and the output of: gnome-control-center -v bluetooth If all else fails, you can run "hciconfig hci0 up" and try to reproduce the problem, because I can't figure out why it's not working. Oh, and you're running this under GNOME with gnome-settings-daemon running as well, right?
[root@f22m chris]# gdbus introspect --system --dest org.bluez --object-path /org/bluez/hci0 node /org/bluez/hci0 { }; [root@f22m chris]# gnome-control-center -v bluetooth (gnome-control-center:2682): GLib-GObject-WARNING **: The property GtkCellRendererPixbuf:follow-state is deprecated and shouldn't be used anymore. It will be removed in a future version. ** (gnome-control-center:2682): DEBUG: Enabling debugging ** (gnome-control-center:2682): DEBUG: No extra argument (gnome-control-center:2682): Bluetooth-DEBUG: Default adapter changed (gnome-control-center:2682): GLib-GIO-CRITICAL **: g_dbus_proxy_get_cached_property: assertion 'G_IS_DBUS_PROXY (proxy)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed (gnome-control-center:2682): GLib-GIO-CRITICAL **: g_dbus_proxy_get_cached_property: assertion 'G_IS_DBUS_PROXY (proxy)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed (gnome-control-center:2682): GLib-GIO-CRITICAL **: g_dbus_proxy_get_cached_property: assertion 'G_IS_DBUS_PROXY (proxy)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (gnome-control-center:2682): GLib-CRITICAL **: g_variant_unref: assertion 'value != NULL' failed (gnome-control-center:2682): bluetooth-cc-panel-DEBUG: Updating airplane mode: has_airplane_mode 0, hardware_airplane_mode 0, airplane_mode 0 (gnome-control-center:2682): bluetooth-cc-panel-DEBUG: No Bluetooth available (gnome-control-center:2682): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gnome-control-center:2682): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed This time, the Bluetooth panel comes up with "No Bluetooth adapters found" So somewhere a regression has occurred as this used to work, maybe Fedora 20 or 21. Maybe I should boot Fedora 22 live image from USB and see if it's a regression within Fedora 22?
OK when I do this one not as root: [chris@f22m ~]$ gnome-control-center -v bluetooth (gnome-control-center:2735): GLib-GObject-WARNING **: The property GtkCellRendererPixbuf:follow-state is deprecated and shouldn't be used anymore. It will be removed in a future version. ** (gnome-control-center:2735): DEBUG: Enabling debugging ** (gnome-control-center:2735): DEBUG: No extra argument (gnome-control-center:2735): Bluetooth-DEBUG: Default adapter changed (gnome-control-center:2735): bluetooth-cc-panel-DEBUG: Updating airplane mode: has_airplane_mode 1, hardware_airplane_mode 0, airplane_mode 0 (gnome-control-center:2735): bluetooth-cc-panel-DEBUG: Bluetooth is available and powered And it now says like before "Devices" and then a big gap, and then "Visible as 'Foobar'" [chris@f22m ~]$ sudo hciconfig hci0 up [sudo] password for chris: Can't init device hci0: Device or resource busy (16) And kernel messages at this same time: [ 405.645478] Bluetooth: hci0: BCM: Read verbose config info failed (-16) It does appear to be running: chris 1983 0.1 0.5 1187300 44488 tty2 Sl+ 18:01 0:00 /usr/libexec/gnome-settings-daemon
(In reply to Chris Murphy from comment #8) <snip> > [chris@f22m ~]$ sudo hciconfig hci0 up > [sudo] password for chris: > Can't init device hci0: Device or resource busy (16) > > And kernel messages at this same time: > [ 405.645478] Bluetooth: hci0: BCM: Read verbose config info failed (-16) OK, the kernel driver is broken, and there's nothing else I can do. Other initial states problems are covered by bug 751483.