Am 08/02/12, schrieb Stefan Seyfried :

Am 02.08.2012 06:41, schrieb Will Stephenson:

...

On Friday 27 Jul 2012 19:32:47 Stefan Seyfried wrote:

...

(redirecting to factory again)

...

/etc/udev/rules.d/95-bluez.rules: SUBSYSTEM=="bluetooth", NAME=="hci?", TAG+="systemd", ACTION=="add", \ ENV{SYSTEMD_WANTS}="bluetooth.service"

That's already in upstream systemd: seife@susi:~> grep SYSTEMD_WANTS.*bluetooth /lib/udev/rules.d/* /lib/udev/rules.d/99-systemd.rules:SUBSYSTEM=="bluetooth", TAG+="systemd", ENV{SYSTEMD_WANTS}="bluetooth.target"

But it only works if I "systemctl enable bluetooth.service". And then bluetoothd is always started, no matter if an adapter is present or not...

Are you sure this is not triggered by the 97-bluetooth.rules ? I tried the following on my desktop without bluetooth: add to 99-systemd.rules: KERNEL=="vhci", TAG+="systemd", ENV{SYSTEMD_WANTS}="bluetooth.target" disabled 97-bluetooth.rules enabled bluetooth.service systemctl status bluetooth.service bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/bluetooth.service modprobe hci_vhci -> systemctl status bluetooth.service bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled) Active: active (running) since Thu, 02 Aug 2012 13:42:45 +0200; 33s ago Main PID: 18238 (bluetoothd) CGroup: name=systemd:/system/bluetooth.service └ 18238 /usr/sbin/bluetoothd -n So for me, everything works like it should. Regards, Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org