Bug 396403 – net-wireless/bluez-4.96-r2 udev script doesn't work with systemd

• Status: RESOLVED DUPLICATE of bug 389531
• Product: Gentoo Linux

[Description Igor Poboiko 2011-12-29 12:16:25 UTC]

Bluez installs an "bluetooth.sh" script to "/lib/udev/bluetooth.sh". This scripts tries to run /etc/init.d/bluetooth under some circumstances. 
However if I use systemd as a replacement to openrc, this script doesn't work (because calling /etc/init.d/* script isn't a way to start some service in systemd) and just gives following error message to dmesg:


[   10.815056] /etc/init.d/bluetooth[1982]: You are attempting to run an openrc service on a
[   10.816293] /etc/init.d/bluetooth[1983]: system which openrc did not boot.
[   10.817511] /etc/init.d/bluetooth[1984]: You may be inside a chroot or you may have used
[   10.818725] /etc/init.d/bluetooth[1985]: another initialization system to boot this system.
[   10.819951] /etc/init.d/bluetooth[1986]: In this situation, you will get unpredictable results!
[   10.821196] /etc/init.d/bluetooth[1988]: If you really want to do this, issue the following command:
[   10.822480] /etc/init.d/bluetooth[1989]: touch /lib64/rc/init.d/softlevel

[Comment 1 William Hubbs 2011-12-29 15:27:53 UTC]

(In reply to comment #0)
> Bluez installs an "bluetooth.sh" script to "/lib/udev/bluetooth.sh". This
> scripts tries to run /etc/init.d/bluetooth under some circumstances. 
> However if I use systemd as a replacement to openrc, this script doesn't work
> (because calling /etc/init.d/* script isn't a way to start some service in
> systemd) and just gives following error message to dmesg:
> 
> 
> [   10.815056] /etc/init.d/bluetooth[1982]: You are attempting to run an openrc
> service on a
> [   10.816293] /etc/init.d/bluetooth[1983]: system which openrc did not boot.
> [   10.817511] /etc/init.d/bluetooth[1984]: You may be inside a chroot or you
> may have used
> [   10.818725] /etc/init.d/bluetooth[1985]: another initialization system to
> boot this system.
> [   10.819951] /etc/init.d/bluetooth[1986]: In this situation, you will get
> unpredictable results!
> [   10.821196] /etc/init.d/bluetooth[1988]: If you really want to do this,
> issue the following command:
> [   10.822480] /etc/init.d/bluetooth[1989]: touch /lib64/rc/init.d/softlevel

Udev rules should not be running scripts in /etc/init.d. I recommend fixing bluetooth.sh so that it doesn't do this.

[Comment 2 Pacho Ramos 2011-12-31 20:30:50 UTC]

*** This bug has been marked as a duplicate of bug 389531 ***