22 Mar
2011
22 Mar
'11
7:44 a.m.
On Tue, Mar 22, 2011 at 3:59 AM, Seblu <seblu@seblu.net> wrote:
So, this situation is a bit confusing, so why do not remove /lib/udev/rules.d/97-bluetooth.rules?
I don't think it is a good idea to remove these rules, at they allow bluez to be started on demand rather than unconditionally. I'd rather try to fix it :-) Could you try running "/sbin/udevadm trigger --action=add --type=failed" after dbus has started? Cheers, Tom