https://bugzilla.novell.com/show_bug.cgi?id=796671 https://bugzilla.novell.com/show_bug.cgi?id=796671#c5 --- Comment #5 from Frederic Crozat <fcrozat@suse.com> 2013-01-21 09:02:50 UTC --- (In reply to comment #4)
Isn't udev supposed to set a special tag that causes systemd to start bluetoothd? I think unconditionally enabling bluetoothd is wrong.
systemd udev rules has already such a rule in 99-systemd.rules: SUBSYSTEM=="bluetooth", TAG+="systemd", ENV{SYSTEMD_WANTS}="bluetooth.target" but for this rules to work, bluetooth.service must be "enabled" for bluetooth.target (it isn't by default). Running "systemctl enable bluetooth.service" will not enable bluetooth.service for every boot but only for "bluetooth.target", since its .service file contains : [Install] WantedBy=bluetooth.target and nothing pulls bluetooth.target by default, except the udev systemd rules. I suggest bluez package to unconditionnaly enable bluetooth.service in %post (or just package the symlink to bluetooth.service in /lib/systemd/system/bluetooth.target.wants/ and not rely on presets (which won't work on upgrade, because .service has a different name than initscript, so migration macro won't work). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.