- Edited
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.
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:
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.
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
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)
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.
