Hi Justin:
Justin Mattock wrote:
> For some reason in rules.d
> for the permission setting:
>
> #ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/sbin/bluetoothd --udev"
> to
> RUN+="/usr/sbin/bluetoothd --udev"
> gets this working for me.
> prior to this, udev just would not activate
> bluetoothd
> Anyways thought it would be good to let people know.
>
>
I'm wondering if you are seeing something similar that was happening on
Ubuntu when getting bluez-4.45 added in where the daemon failed to start
upon bootup but works fine later (eg if you hotplug the device).
It turned out that dbus wasn't up and running at the time udev triggered
all devices early in the boot.
The easiest solution was to run:
udevadm trigger --subsystem-match=bluetooth
later on, during an init script or similar.
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@xxxxxxxx
Attachment:
signature.asc
Description: OpenPGP digital signature
