Hmmmmmmmmmmm......
Interestingly this just happened to me too a few minutes ago. Weird.
The device again completely disappeared.
Re-enabled and re-started the service as described w/o success. Several reboots.


Why would /run/dbus/system_bus_socket refuse connection?!
I get the same error.

2020-06-04 21:49:48.535052595  bluetoothd[2544]: Bluetooth daemon 5.54
2020-06-04 21:49:48.535443194  D-Bus setup failed: Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
2020-06-04 21:49:48.535469700  bluetoothd[2544]: Unable to get on D-Bus
2020-06-04 21:50:08.763923696  bluetoothd[1070]: Bluetooth daemon 5.54
2020-06-04 21:50:08.764961887  D-Bus setup failed: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
2020-06-04 21:50:08.764965392  bluetoothd[1070]: Unable to get on D-Bus
The socket is there just fine. Shouldn't throw this error to begin with.

On my end it's even worse now. The device is actually really gone:
marian@ obarun ~ % btmgmt
[mgmt]# info
Index list with 0 items
marian@ obarun ~ % dmesg | grep Bluetooth
[    6.691990] Bluetooth: Core ver 2.22
[...]
[    8.870964] Bluetooth: hci0: command 0x0c03 tx timeout
[...]
[   16.764242] Bluetooth: hci0: sending initial HCI reset command failed (-110)
What the hell. This is worrisome,...before this, the card got recognized by Windows and Linux. Windows could even use and manage it, Linux could at least recognize it's there. Now it's not. Maybe this time it's not Eric's fault? (I bet it is!) :D
On my machine I could suspect the dual boot thing and Windows and Linux constantly pairing the device. Maybe the card got tired? Burn out? Wants to retire? It's not 65 yet!


@ dvam
What bluetooth card model do you have? Do you dual-boot? Do you triple boot? Have you noticed anything weird before it happened?
The only thing I did today was disabling/enabling the device once today (in Obarun) to pair with my speaker and after a reboot a lot later it's gone. Hm..

@ eric : don't worry about me...
@ dvam : I solved this on my end by removing and re-installing the NIC (Intel Dual Wireless 7260 mini-PCIe) (Sophisticated solution there...)

P.S.: I used these instructions on how to share the same key pairs among OSes to avoid having to pair over and over again.
please update the dbus-66serv and enable it again:
# 66-enable -F -t <tree_name> dbus
It should solve the permissions issue
thanks, it was so sobering experience ... bluetoothd was successfully updated and enabled, but update of dbus-66serv to 0.1.5-1 caused a failed login after the reboot
login: trying to run a sulogin command
Give root password for maintenance
(or press Control-D to continue):  sulogin: cannot read /dev/tty1: operation not permited
and that led to desktop where all root services are down, so I downgrade to 0.1.3-1, and all is as it should be.

P.S. environment lines in dbus-session@ file should end with dbus, please check ...
update again and force the overwrite of the configuration file and tell me
# 66-enable -F -C -t <tree> dbus
# 66-start -R -t <tree> dbus
do the same for your dbus-session

Edit: be sure to use the 0.0.5.1 66-tools version
all is ok! ... I did exactly what you asked ... it was a little bit rough, but 0.1.6-1 is good one ... thanks.
a year later
I don't have the ability to see other devices or connect to them. I have read through this thread to the best of my ability and tried all of the commands, and am certain I have all the correct packages and all of the parts of the system are connected to each other and can 'see' my device. But scanning never finds anything else.

Can anyone please help me? Just tell me what input or ouput I need to provide in order to get some assistance. Many thanks in advance
4 months later
*bump*

I could really use a few pointers here, if anyone is willing. My bluetooth speaker misses his buddies Metallica
provide logs of your service.
3 months later

Powered by Obarun