В Fri, 20 Dec 2013 12:30:23 -0300 Cristian Rodríguez пишет:

El 20/12/13 07:31, ianseeks escribió:

...

HI

Does anyone know how this gets started? I've deconfigured it from System Settings/Startup and Shutdown and its not loaded via Yast/System Services Run Level.

Mind you "Yast/System Services Run Level" seems to be in a bit of a flakey state on 12.3, i can't select a run level, the drop down to choose 1-5 is blank.

systemctl enable bluetooth.service

Is not it supposed to be started automatically by udev if bluetooth devices are present? /usr/lib/udev/rules.d/99-systemd.rules:SUBSYSTEM=="bluetooth", TAG+="systemd", ENV{SYSTEMD_WANTS}+="bluetooth.target" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Fri, 20 Dec 2013 13:24:04 -0300 Cristian Rodríguez пишет:

El 20/12/13 13:05, Andrey Borzenkov escribió:

...

В Fri, 20 Dec 2013 12:30:23 -0300 Cristian Rodríguez пишет:

...

El 20/12/13 07:31, ianseeks escribió:

...

HI

Does anyone know how this gets started? I've deconfigured it from System Settings/Startup and Shutdown and its not loaded via Yast/System Services Run Level.

Mind you "Yast/System Services Run Level" seems to be in a bit of a flakey state on 12.3, i can't select a run level, the drop down to choose 1-5 is blank.

systemctl enable bluetooth.service

Is not it supposed to be started automatically by udev if bluetooth devices are present?

apparently there is a problem with that, as the post scriptlets say:

# We need the bluez systemd service enabled at any time. It won't start up # on it's own, as it is triggered by udev in the end (bnc#796671) /bin/systemctl enable bluetooth.service 2>&1 || : /bin/systemctl daemon-reload >/dev/null 2>&1 || :

Ah, right. It still has to be enabled. It would be more clean to simply package static link, as there is really no reason for it to be manually enabled/disabled. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Fri, 20 Dec 2013 17:16:24 +0000 ianseeks пишет:

I've now tried " systemctl disable bluetooth.service" to stop it, can i stop it starting up again unless i specifically ask it?

"systemctl disable" should do it at least until next bluez update ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 20/12/13 14:16, ianseeks escribió: can i stop

it starting up again unless i specifically ask it?

Yes, use "mask" instead of "disable" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Сб, 21/12/2013 в 10:26 +0000, ianseeks пишет:

On Friday 20 Dec 2013 14:36:36 Cristian Rodríguez wrote:

...

El 20/12/13 14:16, ianseeks escribió:

can i stop

...

it starting up again unless i specifically ask it?

Yes, use "mask" instead of "disable" Thanks, had a look at that via "man" and it says it obeys the "-runtime" flag so only works until the next reboot.

Sorry? mask is persistent _unless_ you use --runtime. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org