http://bugzilla.opensuse.org/show_bug.cgi?id=987114 http://bugzilla.opensuse.org/show_bug.cgi?id=987114#c1 Bjørn Lie <zaitor@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |damien.lloyd21@gmail.com, | |zaitor@opensuse.org Flags| |needinfo?(damien.lloyd21@gm | |ail.com) --- Comment #1 from Bjørn Lie <zaitor@opensuse.org> --- What is the output of the following command in a terminal window ... zypper search --installed --details bluetooth ... I suspect you are missing pulseaudio-module-bluetooth -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 http://bugzilla.opensuse.org/show_bug.cgi?id=987114#c3 --- Comment #3 from Bjørn Lie <zaitor@opensuse.org> --- Ok so you have what should be needed from the GNOME side. Does gnome-bluetooth in gnome-control-center identify the headset as a head-set after pairing? Please remove the pairing again, reboot, pair the headset again. Then as root, do journalctl -b Attach the log you get here please. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 http://bugzilla.opensuse.org/show_bug.cgi?id=987114#c5 --- Comment #5 from Damien Lloyd <damien.lloyd21@gmail.com> --- (In reply to Bjørn Lie from comment #3)

Ok so you have what should be needed from the GNOME side.

Does gnome-bluetooth in gnome-control-center identify the headset as a head-set after pairing?

Please remove the pairing again, reboot, pair the headset again. Then as root, do journalctl -b

Attach the log you get here please.

I've followed your steps; gnome-bluetooth does recognise my headset as such. I ttached a file which contains the output of 'journalctl -b'. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 http://bugzilla.opensuse.org/show_bug.cgi?id=987114#c7 --- Comment #7 from Damien Lloyd <damien.lloyd21@gmail.com> --- (In reply to Bjørn Lie from comment #6)

Jun 30 10:07:46 linux-51ni bluetoothd[1042]: Bluetooth daemon 5.40 Jun 30 10:07:46 linux-51ni bluetoothd[1042]: Starting SDP server Jun 30 10:07:46 linux-51ni bluetoothd[1042]: Bluetooth management interface 1.12 initialized Jun 30 10:07:46 linux-51ni bluetoothd[1042]: Failed to obtain handles for "Service Changed" characteristic Jun 30 10:07:46 linux-51ni bluetoothd[1042]: Sap driver initialization failed. Jun 30 10:07:46 linux-51ni bluetoothd[1042]: sap-server: Operation not permitted (1) Jun 30 10:07:49 linux-51ni bluetoothd[1042]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource Jun 30 10:07:49 linux-51ni bluetoothd[1042]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink Jun 30 10:07:58 linux-51ni bluetoothd[1042]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSource Jun 30 10:07:58 linux-51ni bluetoothd[1042]: Endpoint registered: sender=:1.52 path=/MediaEndpoint/A2DPSink Jun 30 10:07:58 linux-51ni bluetoothd[1042]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Jun 30 10:09:04 linux-51ni bluetoothd[1042]: a2dp-source profile connect failed for 88:C6:26:89:0C:24: Device or resource busy Jun 30 10:09:04 linux-51ni bluetoothd[1042]: /org/bluez/hci0/dev_88_C6_26_89_0C_24/fd0: fd(34) ready

Do you have other bluetooth things connected currently? Asking since it states that the address is already in use.

My phone was connected to the bluetooth headset, but I realised that I had to update my UE MEGABOOM through my phone, which I did. After restarting, I was able to play music through my headset on my laptop but restarting it causes the headset to not show up again under 'Sound Settings' unless I remove the headset from gnome-bluetooth and connect/pair it again. So, the update to my headset helped partially solve the issue, but there still is a problem in that the bluetooth headset still won't always appear under 'Sound Settings' unless I disconnect/connect it again. So far, the headset is the only bluetooth device my laptop is connected to. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 http://bugzilla.opensuse.org/show_bug.cgi?id=987114#c10 Christian Imhorst <christian.imhorst@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.imhorst@gmail.com --- Comment #10 from Christian Imhorst <christian.imhorst@gmail.com> --- Same issue here, but with Leap 15.0. Headset is paired but does not show up in Gnome sound settings. My headset is connected and paired: [cha cha 2]# info Device E1:82:56:DC:3E:51 (public) Name: cha cha 2 Alias: cha cha 2 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) RSSI: -44 But PulseAudio cannot show the headset as sound device. It only shows the internal speakers of my laptop, so I cannot select the headset to play sound on it: $ pacmd list-cards 1 card(s) available. index: 0 name: <alsa_card.pci-0000_00_1b.0> driver: <module-alsa-card.c> owner module: 6 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xe2720000 irq 36" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1b.0" sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Internes Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" [etc...] But maybe it's not a problem with bluetooth but with pulseaudio 11.1? $ pulseaudio --version pulseaudio 11.1-rebootstrapped I tried the fix from: https://bugzilla.suse.com/show_bug.cgi?id=1058053 and addes this line load-module module-bluetooth-discover autodetect_mtu=false to /etc/pulse/default.pa but without success. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 Sébastien POHER <sogal@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sogal@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 http://bugzilla.opensuse.org/show_bug.cgi?id=987114#c14 --- Comment #14 from Dev Guy <devguy.ca@gmail.com> --- I am seeing a similar problem of TW, using KDE. I connect my W-King mini bluetooth speaker to PC. The device makes a sound when connected to, or disconnected. When I go to audio setting to select it as the output device, it is not shown under "Playback devices". However my bluetooth DAC does appear and works. I have tired re-connecting, as well as creating a new connection, has not helped. I even logged out and back in. Each time I disconnect and reconnect to the device, it make a sound so I know there is a connection there. Here is the scan showing detection of the W-King speaker when it's turned on: $ bluetoothctl scan on Discovery started [CHG] Controller 00:1B:10:00:2A:EC Discovering: yes [CHG] Device F4:4E:FC:62:C3:70 Connected: yes [NEW] Endpoint /org/bluez/hci0/dev_F4_4E_FC_62_C3_70/sep1 [NEW] Endpoint /org/bluez/hci0/dev_F4_4E_FC_62_C3_70/sep2 [NEW] Endpoint /org/bluez/hci0/dev_F4_4E_FC_62_C3_70/sep3 [NEW] Endpoint /org/bluez/hci0/dev_F4_4E_FC_62_C3_70/sep4 [NEW] Transport /org/bluez/hci0/dev_F4_4E_FC_62_C3_70/fd8 List of devices: $ bluetoothctl devices Device F4:4E:FC:62:C3:70 W-KING D8 mini-1 Device 1C:E6:1D:5C:72:CD Dev's Galaxy S20 FE 5G $ uname -a Linux source 6.0.8-1-default #1 SMP PREEMPT_DYNAMIC Fri Nov 11 08:02:50 UTC 2022 (1579d93) x86_64 x86_64 x86_64 GNU/Linux $ sudo zypper search -i --details bluetooth Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+-----------------------------+---------+-----------------+--------+---------------------- i+ | kernel-firmware-bluetooth | package | 20221031-1.1 | noarch | Main Repository (OSS) i+ | libbluetooth3 | package | 5.65-4.1 | x86_64 | Main Repository (OSS) i | libQt5Bluetooth5 | package | 5.15.7+kde5-1.1 | x86_64 | Main Repository (OSS) i | libQt5Bluetooth5-imports | package | 5.15.7+kde5-1.1 | x86_64 | Main Repository (OSS) i | NetworkManager-bluetooth | package | 1.40.2-2.1 | x86_64 | Main Repository (OSS) i+ | pulseaudio-module-bluetooth | package | 16.1-1.3 | x86_64 | Main Repository (OSS) -- You are receiving this mail because: You are on the CC list for the bug.