On Wed, 8 Feb 2017 09:42:48 -0800 Rick Stevens wrote:
[ ... ]
Do you have bluetoothd running? Check by
systemctl status bluetooth.service
Yes, see
]# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset:
enabled)
Active: active (running) since Thu 2017-02-09 16:47:45 CET; 1min 45s ago
Docs: man:bluetoothd(8)
Main PID: 8126 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
└─8126 /usr/libexec/bluetooth/bluetoothd
Feb 09 16:47:45 siffux systemd[1]: Stopped Bluetooth service.
Feb 09 16:47:45 siffux systemd[1]: Starting Bluetooth service...
Feb 09 16:47:45 siffux bluetoothd[8126]: Bluetooth daemon 5.43
Feb 09 16:47:45 siffux systemd[1]: Started Bluetooth service.
Feb 09 16:47:45 siffux bluetoothd[8126]: Starting SDP server
Feb 09 16:47:45 siffux bluetoothd[8126]: Bluetooth management interface 1.14 initialized
Feb 09 16:47:45 siffux bluetoothd[8126]: Failed to set mode: Blocked through rfkill
(0x12)
Feb 09 16:47:45 siffux bluetoothd[8126]: Endpoint registered: sender=:1.27
path=/MediaEndpoint/A2DPSource
Feb 09 16:47:45 siffux bluetoothd[8126]: Endpoint registered: sender=:1.27
path=/MediaEndpoint/A2DPSink
The "Blocked through rfkill" made me wonder.
I immediately did
# rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
And now I'm completely confused.
--Frank Elsner