Created attachment 312413 [details] emerge --info bluez Starting /etc/init.d/bluetoothd the result on CLI is * Udev coldplug of bluetooth devices ... [ OK ] pgrep blue finds nothing, then /etc/init.d/bluetooth stop causes status to go from "started" to "stopped", but dos not print anything by itsself.
Needless to mention, applications trying to find org.bluez on dbus fail. Example simple-agent: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
Here is some instruction how to proceed when something wrong happens with bluetoothd: 1. Try to run it manually e.g. sudo bluetoothd -dn 2. Check if there is an adapter plugged with hciconfig, if there is none this is probably a driver/kernel problem. 3. Unplug/plug the adapter again, if it is not a dongle try software or hardware rfkill. 4. Try resetting using hciconfig hci0 reset If none of this works, send an email to linux-bluetooth explaining the problem and adding the logs, syslog, hcidump, dmesg, etc that could help solving the problem.
Thank you. It was my mistake, I had no firmware and therefore no device, as you said.
