http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c1 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org, | |msuchanek@suse.com Flags| |needinfo?(msuchanek@suse.co | |m) --- Comment #1 from Dominique Leuenberger --- Can you please, from a console, start

gnome-control-center -v bluetooth

and paste the output here (with the dongle connectedl the entire bluetoothctl and hciconfig stuff should not be needed: GNOME should handle that when it manages to find the hardware) As for - install pulseaudio BT module This module is recommended by the GNOME Basis pattern already; a default GNOME install should get this -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c3 Michal Suchanek changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msuchanek@suse.co | |m) | --- Comment #3 from Michal Suchanek --- Created attachment 702245 --> http://bugzilla.opensuse.org/attachment.cgi?id=702245&action=edit control center log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c5 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |sebastian.parschauer@suse.c | |om Version|Leap 42.2 |Leap 42.3 --- Comment #5 from Sebastian Parschauer --- I've got the same problem on Leap 42.3. The Bluetooth settings start discovering Bluetooth devices but don't show any Bluetooth device. It can be checked with running bluetoothctl in parallel. $ bluetoothctl [NEW] Controller 00:11:B1:07:A3:62 myhostname [default] [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001112-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001106-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001105-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001104-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00005005-0000-1000-8000-0002ee000001 [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001133-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 UUIDs: 00001132-0000-1000-8000-00805f9b34fb [CHG] Controller 00:11:B1:07:A3:62 Class: 0x1c0104 [CHG] Controller 00:11:B1:07:A3:62 Powered: yes # run GNOME bluetooth settings in parallel [CHG] Controller 00:11:B1:07:A3:62 Discoverable: yes [CHG] Controller 00:11:B1:07:A3:62 DiscoverableTimeout: 0x000000 [CHG] Controller 00:11:B1:07:A3:62 DiscoverableTimeout: 0x000000 [CHG] Controller 00:11:B1:07:A3:62 Discovering: yes [NEW] Device FC:58:FA:11:7C:23 QS1 [bluetooth]# connect FC:58:FA:11:7C:23 Attempting to connect to FC:58:FA:11:7C:23 [CHG] Device FC:58:FA:11:7C:23 Connected: yes [CHG] Device FC:58:FA:11:7C:23 UUIDs: 00001108-0000-1000-8000-00805f9b34fb [CHG] Device FC:58:FA:11:7C:23 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb [CHG] Device FC:58:FA:11:7C:23 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Device FC:58:FA:11:7C:23 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Device FC:58:FA:11:7C:23 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb [CHG] Device FC:58:FA:11:7C:23 Paired: yes Connection successful Afterward I can use my QS1 Bluetooth headphones from the sound settings. This is the proof that Bluetooth is working and only the GNOME Bluetooth settings don't show the Bluetooth devices. My controller:

Bus 003 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

$ hciconfig -a hci0 hci0: Type: Primary Bus: USB BD Address: 00:11:B1:07:A3:62 ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING RX bytes:600 acl:0 sco:0 events:39 errors:0 TX bytes:425 acl:0 sco:0 commands:37 errors:0 Features: 0xff 0xff 0x8f 0xf8 0x18 0x18 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'myhostname' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 1.2 (0x2) Revision: 0x639 LMP Version: 1.2 (0x2) Subversion: 0x639 Manufacturer: Cambridge Silicon Radio (10) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c7 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(msuchanek@suse.co | |m) --- Comment #7 from Sebastian Parschauer --- @Michal: Which controller do you have? Can you please provide lsusb and "hciconfig -a hci0" output? TIA -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c9 --- Comment #9 from Sebastian Parschauer --- It also works with blueman for me. A workaround might be installing and using that one. It uses the BlueZ API. Especially if you don't run GNOME, then this should work fine for you. But as all other tools work properly, this is a GNOME bug and should be fixed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c11 --- Comment #11 from Michal Suchanek --- If it needs a service to run it should start it. Clearly it does not need the gnome-shell/unity running to display. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c13 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #13 from Sebastian Parschauer --- I'm running GNOME and it is broken for me. So reopening. I've even located the bug in panels/bluetooth/cc-bluetooth-panel.c: 145 if (self->priv->has_airplane_mode == FALSE) { 146 g_debug ("No Bluetooth available"); 147 sensitive = FALSE; 148 powered = FALSE; 149 page = BLUETOOTH_NO_DEVICES_PAGE; ... 166 } else { 167 g_debug ("Bluetooth is available and powered"); 168 sensitive = TRUE; 169 powered = TRUE; 170 page = BLUETOOTH_WORKING_PAGE; 171 } As my workstation has no airplane mode, this will always show no devices for me. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c15 --- Comment #15 from Sebastian Parschauer --- $ sudo rfkill list 5: hci0: Bluetooth Soft blocked: no Hard blocked: no -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c17 --- Comment #17 from Sebastian Parschauer --- $ gdbus introspect --session --dest org.gnome.SettingsDaemon.Rfkill --object-path /org/gnome/SettingsDaemon/Rfkill --only-properties node /org/gnome/SettingsDaemon/Rfkill { @org.freedesktop.DBus.GLib.CSymbol("gsd_rfkill_manager") interface org.gnome.SettingsDaemon.Rfkill { properties: readwrite b AirplaneMode = false; readonly b HardwareAirplaneMode = false; readonly b HasAirplaneMode = false; readonly b ShouldShowAirplaneMode = false; readwrite b BluetoothAirplaneMode = false; readonly b BluetoothHardwareAirplaneMode = false; readonly b BluetoothHasAirplaneMode = false; }; }; -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c19 --- Comment #19 from Michal Suchanek --- gdbus introspect --session --dest org.gnome.SettingsDaemon.Rfkill --object-path /org/gnome/SettingsDaemon/Rfkill --only-properties Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Rfkill was not provided by any .service files -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c21 --- Comment #21 from Dominique Leuenberger --- (In reply to Michal Suchanek from comment #19)

gdbus introspect --session --dest org.gnome.SettingsDaemon.Rfkill --object-path /org/gnome/SettingsDaemon/Rfkill --only-properties Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Rfkill was not provided by any .service files

you don't run a GNOME session - there is no GNOME settings daemon running. Let's not pollute this bug further with this, shall we? I'd like to focus on the people having a valid problem -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c23 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sebastian.parscha | |uer@suse.com) | --- Comment #23 from Sebastian Parschauer --- Okay, I've found the bug in the gnome-settings-daemon. It only sets these properties at startup (see: plugins/rfkill/rfkill-glib.c, cc_rfkill_glib_open()). So USB Bluetooth dongles must be connected when starting the GNOME session. This is not really how USB is intended to be used. My expectation was that I can connect the device when I need it and keep it disconnected when I don't need it. I have especially the current Bluetooth kernel stack CVE in mind. With the dongle connected at startup it works. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 http://bugzilla.opensuse.org/show_bug.cgi?id=1004830#c25 --- Comment #25 from Sebastian Parschauer --- Once the bug appears, it can also be fixed by restarting the gnome-settings-daemon. -- You are receiving this mail because: You are on the CC list for the bug.