[Bug 1175536] New: Bluetooth connection is no longer working
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 Bug ID: 1175536 Summary: Bluetooth connection is no longer working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: duelistgamer@yahoo.co.in QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After updating to the first Tumbleweed snapshot containing kernel 5.8, my bluetooth connection is no longer functioning correctly. 1. On connecting to a bluetooth audio device after booting, the connection is fine. 2. On disconnecting and reconnecting to the same device, the connection doesn't seem to work and the audio device does not indicate that it has received a connection. 3. On wiping all saved bluetooth devices and adding new ones, the search function appears to behave strangely and add ALL bluetooth devices that it is able to detect, not just the one device I want to connect to. 4. It fails to pair any new bluetooth device that I want to connect after this. My tumbleweed machine is a Thinkpad T460p, configured with an i7 6820HQ CPU. lspci result: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x4) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation QM170 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31) 02:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2) 03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 Aayush Agarwal <duelistgamer@yahoo.co.in> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |duelistgamer@yahoo.co.in -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 http://bugzilla.opensuse.org/show_bug.cgi?id=1175536#c2 --- Comment #2 from Aayush Agarwal <duelistgamer@yahoo.co.in> --- Created attachment 840943 --> http://bugzilla.opensuse.org/attachment.cgi?id=840943&action=edit Bluetooth dmesg Takashi, it seems my original report was inaccurate. The error persists regardless of which kernel version I am on. dmesg indicates a segmentation fault in bluetoothd. Pairing new devices also fails. I've attached the dmesg output for kernel 5.8 segmentation fault and kernel 5.7 segmentation fault+failed pairing. The fault code seems to be identical for both kernels. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 http://bugzilla.opensuse.org/show_bug.cgi?id=1175536#c3 Aayush Agarwal <duelistgamer@yahoo.co.in> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(duelistgamer@yaho | |o.co.in) | --- Comment #3 from Aayush Agarwal <duelistgamer@yahoo.co.in> --- Created attachment 840944 --> http://bugzilla.opensuse.org/attachment.cgi?id=840944&action=edit Hardware information as output by hwinfo Hardware information attached. Hopefully these two are enough, but please let me know if I can provide more info. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 http://bugzilla.opensuse.org/show_bug.cgi?id=1175536#c6 Aayush Agarwal <duelistgamer@yahoo.co.in> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(duelistgamer@yaho |needinfo?(acho@suse.com) |o.co.in) | --- Comment #6 from Aayush Agarwal <duelistgamer@yahoo.co.in> --- Sorry for the delay; just moved to the 20200826 snapshot. I couldn't find the bluetooth directory in /usr/lib. Has it changed? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 http://bugzilla.opensuse.org/show_bug.cgi?id=1175536#c7 Al Cho <acho@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(acho@suse.com) |needinfo?(duelistgamer@yaho | |o.co.in) --- Comment #7 from Al Cho <acho@suse.com> --- (In reply to Aayush Agarwal from comment #6)
Sorry for the delay; just moved to the 20200826 snapshot. I couldn't find the bluetooth directory in /usr/lib. Has it changed?
No, it's not, and it's weird .... You can use "rpm -ql bluez" to find where is it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 http://bugzilla.opensuse.org/show_bug.cgi?id=1175536#c8 Aayush Agarwal <duelistgamer@yahoo.co.in> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(duelistgamer@yaho |needinfo? |o.co.in) | --- Comment #8 from Aayush Agarwal <duelistgamer@yahoo.co.in> --- (In reply to Al Cho from comment #7)
(In reply to Aayush Agarwal from comment #6)
Sorry for the delay; just moved to the 20200826 snapshot. I couldn't find the bluetooth directory in /usr/lib. Has it changed?
No, it's not, and it's weird .... You can use "rpm -ql bluez" to find where is it.
It seems that bluetooth has been moved to libexec. On running "/usr/libexec/bluetooth/bluetoothd -d" I am getting: D-Bus setup failed: Name already in use Apologies for the very newbie-ish situation, but I am completely unfamiliar with the workings of D-Bus. I don't know how to temporarily remove it and restore it again. I did try some things in https://askubuntu.com/questions/723671/d-bus-setup-failed-name-already-in-us... But I probably got it wrong, because D-Bus still complained that the name was already in use after rfkill block, systemctl stop and /usr/libexec/ -d. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 http://bugzilla.opensuse.org/show_bug.cgi?id=1175536#c9 Al Cho <acho@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? |needinfo?(duelistgamer@yaho | |o.co.in) --- Comment #9 from Al Cho <acho@suse.com> --- (In reply to Aayush Agarwal from comment #8)
(In reply to Al Cho from comment #7)
(In reply to Aayush Agarwal from comment #6)
Sorry for the delay; just moved to the 20200826 snapshot. I couldn't find the bluetooth directory in /usr/lib. Has it changed?
No, it's not, and it's weird .... You can use "rpm -ql bluez" to find where is it.
It seems that bluetooth has been moved to libexec.
On running "/usr/libexec/bluetooth/bluetoothd -d" I am getting:
D-Bus setup failed: Name already in use
Apologies for the very newbie-ish situation, but I am completely unfamiliar with the workings of D-Bus. I don't know how to temporarily remove it and restore it again. I did try some things in https://askubuntu.com/questions/723671/d-bus-setup-failed-name-already-in-us...
But I probably got it wrong, because D-Bus still complained that the name was already in use after rfkill block, systemctl stop and /usr/libexec/ -d.
Basically you can use "kill <pid>" to kill the process pid and run "/usr/libexec/bluetooth/bluetoothd -d" ... that should works. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 http://bugzilla.opensuse.org/show_bug.cgi?id=1175536#c10 Aayush Agarwal <duelistgamer@yahoo.co.in> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(duelistgamer@yaho | |o.co.in) | --- Comment #10 from Aayush Agarwal <duelistgamer@yahoo.co.in> --- (In reply to Al Cho from comment #9)
(In reply to Aayush Agarwal from comment #8)
(In reply to Al Cho from comment #7)
(In reply to Aayush Agarwal from comment #6)
Sorry for the delay; just moved to the 20200826 snapshot. I couldn't find the bluetooth directory in /usr/lib. Has it changed?
No, it's not, and it's weird .... You can use "rpm -ql bluez" to find where is it.
It seems that bluetooth has been moved to libexec.
On running "/usr/libexec/bluetooth/bluetoothd -d" I am getting:
D-Bus setup failed: Name already in use
Apologies for the very newbie-ish situation, but I am completely unfamiliar with the workings of D-Bus. I don't know how to temporarily remove it and restore it again. I did try some things in https://askubuntu.com/questions/723671/d-bus-setup-failed-name-already-in-us...
But I probably got it wrong, because D-Bus still complained that the name was already in use after rfkill block, systemctl stop and /usr/libexec/ -d.
Basically you can use "kill <pid>" to kill the process pid and run "/usr/libexec/bluetooth/bluetoothd -d" ... that should works.
If I kill the bluetoothd process, it automatically restarts. This is even after I rfkill block bluetooth and switch it off from the KDE UI. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175536 http://bugzilla.opensuse.org/show_bug.cgi?id=1175536#c11 Aayush Agarwal <duelistgamer@yahoo.co.in> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(acho@suse.com) --- Comment #11 from Aayush Agarwal <duelistgamer@yahoo.co.in> --- (In reply to Aayush Agarwal from comment #10)
(In reply to Al Cho from comment #9)
(In reply to Aayush Agarwal from comment #8)
(In reply to Al Cho from comment #7)
(In reply to Aayush Agarwal from comment #6)
Sorry for the delay; just moved to the 20200826 snapshot. I couldn't find the bluetooth directory in /usr/lib. Has it changed?
No, it's not, and it's weird .... You can use "rpm -ql bluez" to find where is it.
It seems that bluetooth has been moved to libexec.
On running "/usr/libexec/bluetooth/bluetoothd -d" I am getting:
D-Bus setup failed: Name already in use
Apologies for the very newbie-ish situation, but I am completely unfamiliar with the workings of D-Bus. I don't know how to temporarily remove it and restore it again. I did try some things in https://askubuntu.com/questions/723671/d-bus-setup-failed-name-already-in-us...
But I probably got it wrong, because D-Bus still complained that the name was already in use after rfkill block, systemctl stop and /usr/libexec/ -d.
Basically you can use "kill <pid>" to kill the process pid and run "/usr/libexec/bluetooth/bluetoothd -d" ... that should works.
If I kill the bluetoothd process, it automatically restarts. This is even after I rfkill block bluetooth and switch it off from the KDE UI.
The problem is still present in the latest snapshot. Killing bluethoothd is ineffective because the program automatically restarts. Is there some way to prevent that so that I could run bluetoothd with debugging option flag? Thank you. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com