Le 17/11/2012 05:28, Michael Biebl a écrit :
I think when bluez is run under systemd, it should disable
/lib/udev/rules.d/97-bluetooth.rules and rather start the bluetooth
service by hooking up in bluetooth.target.
I've CCed the bluez maintainer for his input on this.
I haven't tried what you asked yet, but I still have something to notice:
(1) if I start as usual, then bluetooth isn't enabled automatically,
that is what my bug report is about ;
(2) but you have to notice that "starting as usual" means "the adaptater
is already in the USB socket"!
(3) so after startup with the adaptater in the socket, if I remove it
and reinsert it, then bluetooth starts working! [alternatively, I can
"service bluetooth start", which is what I was doing until then]
So the impression I have is that systemd/udev/whatever knows about USB
bluetooth adaptaters only when some event occurs : if no event occurs,
then it goes unseen, and bluetooth stays disabled.
Do you still want me to mess around with udev, or does this clear
matters already?
Snark on #debian-science
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
