Arch Linux

CBiX

Member

Registered: 2013-07-15

Posts: 21

Gnome issue with bluetoothd

I hope this is the right forum, because the problem is probably not in the bluetooth stack but in Gnome.

Due to traveling I started using both a bluetooth speaker and keyboard with my arch laptop. When I configure these devices with gnome-control-center, they initially work almost perfectly together. But when I go to a different gnome-control-center panel or close it and open again, the settings can't connect to the bluetooth backend anymore. The devices sometimes stop working and I can't access any bluetooth settings unless I restart the bluetooth system service.

I guess I had similar issues before, but was never really using bluetooth productively.

When I avoid using gnome settings and configure the devices through `bluetoothctl`, I don't have this issue but instead the keyboard starts lagging and disconnecting frequently. Anyways I want to be able to configure bluetooth devices through Gnome

gnome-control-center 3.28.1-1
gnome-bluetooth 3.28.0-1
bluez 5.49-3

Apr 29 12:30:15 FlohkisteArch systemd[1]: Starting Bluetooth service...
Apr 29 12:30:15 FlohkisteArch bluetoothd[3146]: Bluetooth daemon 5.49
Apr 29 12:30:15 FlohkisteArch systemd[1]: Started Bluetooth service.
Apr 29 12:30:15 FlohkisteArch bluetoothd[3146]: Starting SDP server
Apr 29 12:30:15 FlohkisteArch bluetoothd[3146]: Bluetooth management interface 1.14 initialized
Apr 29 12:30:15 FlohkisteArch bluetoothd[3146]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource
Apr 29 12:30:15 FlohkisteArch bluetoothd[3146]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink
Apr 29 12:30:15 FlohkisteArch bluetoothd[3146]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSource
Apr 29 12:30:15 FlohkisteArch bluetoothd[3146]: Endpoint registered: sender=:1.58 path=/MediaEndpoint/A2DPSink
Apr 29 12:31:20 FlohkisteArch bluetoothd[3146]: /org/bluez/hci0/dev_78_44_05_E0_D2_E2/fd0: fd(60) ready
Apr 29 12:31:20 FlohkisteArch bluetoothd[3146]: Browsing: connect error: Connection refused (111)
Apr 29 12:33:34 FlohkisteArch bluetoothd[3146]: Failed to set mode: Failed (0x03)

[ 3060.155323] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3076.120339] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3097.993529] hid-generic 0005:0A5C:8502.0002: unknown main item tag 0x0
[ 3097.993707] input: Bluetooth Keyboard as /devices/virtual/misc/uhid/0005:0A5C:8502.0002/input/input27
[ 3097.995396] hid-generic 0005:0A5C:8502.0002: input,hidraw0: BLUETOOTH HID v0.01 Keyboard [Bluetooth Keyboard] on 4C:ED:DE:62:A0:04
[ 3102.989418] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3118.986357] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3124.783502] input: 78:44:05:E0:D2:E2 as /devices/virtual/input/input28
[ 3128.987381] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3144.988391] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3160.987428] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3176.987429] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3191.987402] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3207.987449] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3222.989445] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3238.987474] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3239.108683] Bluetooth: hci0: SCO packet for unknown connection handle 49
[ 3239.108696] Bluetooth: hci0: SCO packet for unknown connection handle 49
[ 3251.465452] Bluetooth: hci1: urb 00000000b5e3b03a failed to resubmit (113)
[ 3251.465794] Bluetooth: hci1: urb 00000000dfbdbcb0 failed to resubmit (113)
[ 3258.769485] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3273.989492] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 3289.991501] Bluetooth: hci0: last event is not cmd complete (0x0f)

(gnome-control-center:2793): bluetooth-cc-panel-DEBUG: 12:33:24.569: Updating airplane mode: BluetoothHasAirplaneMode 1, BluetoothHardwareAirplaneMode 0, BluetoothAirplaneMode 0, AirplaneMode 0
(gnome-control-center:2793): bluetooth-cc-panel-DEBUG: 12:33:24.569: Default adapter is unpowered, but should be available
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.591: Not adding device 'FlohkisteArch'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.591: Not interested in device 'FlohkisteArch'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.591: Not interested in device 'FlohkisteArch'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.591: Default adapter changed to: /org/bluez/hci1
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.594: Not interested in device 'FlohkisteArch'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.594: Not interested in device 'FlohkisteArch'
(gnome-control-center:2793): bluetooth-cc-panel-DEBUG: 12:33:24.594: Updating airplane mode: BluetoothHasAirplaneMode 1, BluetoothHardwareAirplaneMode 0, BluetoothAirplaneMode 0, AirplaneMode 0
(gnome-control-center:2793): bluetooth-cc-panel-DEBUG: 12:33:24.594: Default adapter is unpowered, but should be available
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.594: Not interested in device 'FlohkisteArch'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.594: Not adding device 'FlohkisteArch #1'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.595: Adding device Goodis Black Box (/org/bluez/hci1/dev_00_75_58_E7_6E_40)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.595: Saving device type Sprechgarnitur for 00:75:58:E7:6E:40
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.596: Not adding device 'innootech'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.596: Adding device JBL GO (/org/bluez/hci1/dev_78_44_05_7E_84_23)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.596: Saving device type Sprechgarnitur for 78:44:05:7E:84:23
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.598: Not adding device 'DYRE'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.598: Unhandled UUID 00001132-0000-1000-8000-00805f9b34fb (0x1132)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.598: Unhandled UUID 00001800-0000-1000-8000-00805f9b34fb (0x1800)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.598: Unhandled UUID 00001801-0000-1000-8000-00805f9b34fb (0x1801)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.598: Not adding device 'Samsung Galaxy S5'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.599: Not adding device 'Bluetooth Keyboard'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.599: Not adding device 'JBL GO'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.599: Adding device Bluetooth Keyboard (/org/bluez/hci1/dev_10_73_00_13_A7_0E)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.599: Saving device type Tastatur for 10:73:00:13:A7:0E
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Not adding device 'Mixcder ShareMe 5'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Not adding device 'Bose Mini II SoundLink'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Not adding device 'H163'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Unhandled UUID 00001133-0000-1000-8000-00805f9b34fb (0x1133)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Unhandled UUID 00001132-0000-1000-8000-00805f9b34fb (0x1132)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Unhandled UUID 00005005-0000-1000-8000-0002ee000001 (0x5005)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Not adding device 'FlohkisteArch'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Not adding device 'Bluetooth mini Keyboard'
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Adding device JBL GO (/org/bluez/hci1/dev_78_44_05_E0_D2_E2)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.600: Saving device type Sprechgarnitur for 78:44:05:E0:D2:E2
(gnome-control-center:2793): Bluetooth-DEBUG: 12:33:24.630: obexd appeared, registering agent

(gnome-control-center:2793): Bluetooth-WARNING **: 12:33:34.738: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Failed: Failed (g-io-error-quark, 36)
(gnome-control-center:2793): Bluetooth-DEBUG: 12:36:52.526: Unhandled property: rssi

I hope the included logs (journalctl bluetooth, dmesg, gnome-control-center -v) are useful.

CBiX

Member

Registered: 2013-07-15

Posts: 21

Re: Gnome issue with bluetoothd

Is there any good way to debug the gnome bluetooth stack?

LordChaos73

Member

From: .nl

Registered: 2008-11-11

Posts: 183

Re: Gnome issue with bluetoothd

I think bluetooth is somehow broken in Gnome at the moment. Currently, every time I wake this laptop out of suspend mode (or reboot if for that matter), my bluetooth mouse is 'not set up' and I have to register it all over again.

In addition to this I'm seeing these kinds of errors as well:

[28605.114628] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28621.116692] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28637.113564] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28653.004620] Bluetooth: hci0: last event is not cmd complete (0x0f)

Thinkpad X1 Carbon 2nd gen

Linux x1carbon 4.16.11-1-ARCH #1 SMP PREEMPT Tue May 22 21:40:27 UTC 2018 x86_64 GNU/Linux

LONGMAN

Member

Registered: 2018-01-15

Posts: 5

Re: Gnome issue with bluetoothd

Same for me

How we can fix it?

Burlex

Member

From: Russian Moscow

Registered: 2017-03-05

Posts: 4

Re: Gnome issue with bluetoothd

Hello everyone!
I was helped by the package bluez-hid2hci
My configuration:
Dell Inspiron 5378 (intel core i5-7200, Bluetooth Intel(R) Dual Band Wireless-AC 3165 Bluetooth.

LordChaos73

Member

From: .nl

Registered: 2008-11-11

Posts: 183

Re: Gnome issue with bluetoothd

Same for me

How we can fix it?

I "fixed" it by installing Plasma 5.13

LONGMAN

Member

Registered: 2018-01-15

Posts: 5

Re: Gnome issue with bluetoothd

Same for me

How we can fix it?

I "fixed" it by installing Plasma 5.13

So, its not a kernel issue?

LordChaos73

Member

From: .nl

Registered: 2008-11-11

Posts: 183

Re: Gnome issue with bluetoothd

Same for me

How we can fix it?

I "fixed" it by installing Plasma 5.13

So, its not a kernel issue?

I guess not, my bluetooth mouse works fine using Plasma.

CBiX

Member

Registered: 2013-07-15

Posts: 21

Re: Gnome issue with bluetoothd

In addition to this I'm seeing these kinds of errors as well:

[28605.114628] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28621.116692] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28637.113564] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28653.004620] Bluetooth: hci0: last event is not cmd complete (0x0f)

Do you also get these when using Bluetooth with Plasma?

About fix: I once got automatic reconnection with my BT keyboard to work after reboot by a) not using Gnome for Bluetooth setup (bluetoothctl instead, for example) and b) setting

AutoEnable=true

in /etc/bluetooth/main.conf and creating a /etc/bluetooth/input.conf with the following content:

# Configuration file for the input service
# This section contains options which are not specific to any
# particular interface
[General]

# Set idle timeout (in minutes) before the connection will
# be disconnect (defaults to 0 for no timeout)
IdleTimeout=0

#Enable HID protocol handling in userspace input profile
#Defaults to false(hidp handled in hidp kernel module)
UserspaceHID=true

However, this doesn't solve the problem that bluetooth in Gnome is currently broken...

LONGMAN

Member

Registered: 2018-01-15

Posts: 5

Re: Gnome issue with bluetoothd

In addition to this I'm seeing these kinds of errors as well:

[28605.114628] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28621.116692] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28637.113564] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28653.004620] Bluetooth: hci0: last event is not cmd complete (0x0f)

Do you also get these when using Bluetooth with Plasma?

About fix: I once got automatic reconnection with my BT keyboard to work after reboot by a) not using Gnome for Bluetooth setup (bluetoothctl instead, for example) and b) setting

AutoEnable=true

in /etc/bluetooth/main.conf and creating a /etc/bluetooth/input.conf with the following content:

# Configuration file for the input service
# This section contains options which are not specific to any
# particular interface
[General]

# Set idle timeout (in minutes) before the connection will
# be disconnect (defaults to 0 for no timeout)
IdleTimeout=0

#Enable HID protocol handling in userspace input profile
#Defaults to false(hidp handled in hidp kernel module)
UserspaceHID=true

However, this doesn't solve the problem that bluetooth in Gnome is currently broken...

Should we do both "a" and "b" steps?

CBiX

Member

Registered: 2013-07-15

Posts: 21

Re: Gnome issue with bluetoothd

Should we do both "a" and "b" steps?

Yes, but I'm not exactly sure how I did it, I'll try it again later.

Update: Well yea the input.conf is not needed at all, but in bluetoothctl don't forget to enable Trust for your device. And after reboot I need to turn the keyboard off and on.

Last edited by CBiX (2018-06-25 16:36:51)

LONGMAN

Member

Registered: 2018-01-15

Posts: 5

Re: Gnome issue with bluetoothd

I am looking for workaround for gnome bluetooth

LordChaos73

Member

From: .nl

Registered: 2008-11-11

Posts: 183

Re: Gnome issue with bluetoothd

In addition to this I'm seeing these kinds of errors as well:

[28605.114628] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28621.116692] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28637.113564] Bluetooth: hci0: last event is not cmd complete (0x0f)
[28653.004620] Bluetooth: hci0: last event is not cmd complete (0x0f)

Do you also get these when using Bluetooth with Plasma?

No, I no longer see these lines among the kernel debug messages.

LordChaos73

Member

From: .nl

Registered: 2008-11-11

Posts: 183

Re: Gnome issue with bluetoothd

Should we do both "a" and "b" steps?

Yes, but I'm not exactly sure how I did it, I'll try it again later.

Update: Well yea the input.conf is not needed at all, but in bluetoothctl don't forget to enable Trust for your device. And after reboot I need to turn the keyboard off and on.

Even after setting

AutoEnable=true

in /etc/bluetooth/main.conf?

CBiX

Member

Registered: 2013-07-15

Posts: 21

Re: Gnome issue with bluetoothd

Even after setting

AutoEnable=true

in /etc/bluetooth/main.conf?

Yes. AutoEnable just powers the bluetooth interface. If the device doesn't make an attempt to connect (my keyboard does this when it turns on) it doesn't automatically connect. My bluetooth speaker however usually gets automatically connected, probably because it makes more frequent connection attampts to known devices, not sure....

LONGMAN

Member

Registered: 2018-01-15

Posts: 5

Re: Gnome issue with bluetoothd

So, where is the problem? Kernel? Or gnome-shell itself?

alexandro

Member

From: Stockholm, Sweden

Registered: 2018-07-23

Posts: 1

Re: Gnome issue with bluetoothd

Hello everyone!
I was helped by the package bluez-hid2hci
My configuration:
Dell Inspiron 5378 (intel core i5-7200, Bluetooth Intel(R) Dual Band Wireless-AC 3165 Bluetooth.

Thanks . I have installed bluez-hid2hci and bluez-firmware and everything is working well.
Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Last edited by alexandro (2018-07-23 02:00:05)

friendofarch

Member

Registered: 2013-12-30

Posts: 59

Re: Gnome issue with bluetoothd

Same for me

How we can fix it?

I "fixed" it by installing Plasma 5.13

The whole plasma-group or just parts of it? ...and you still use Gnome?

CBiX

Member

Registered: 2013-07-15

Posts: 21

Re: Gnome issue with bluetoothd

Same for me

How we can fix it?

I "fixed" it by installing Plasma 5.13

The whole plasma-group or just parts of it? ...and you still use Gnome?

The problem is the bluetooth configuration interface in gnome and this cannot simply be replaced by this component of plasma. You could probably use Blueman or bluetoothctl on the command line, he refered to switching to Plasma completely.

friendofarch

Member

Registered: 2013-12-30

Posts: 59

Re: Gnome issue with bluetoothd

The problem is the bluetooth configuration interface in gnome and this cannot simply be replaced by this component of plasma.

Thought so.

You could probably use Blueman or bluetoothctl on the command line, he refered to switching to Plasma completely.

I get a connection to my bluetooth speaker via bluetoothctl. The remaining problem is I don't get it activated as an audio device But unless it's somehow connected to this issue I guess I should start a new thread...