/etc/init.d/bluetooth stop claims to shutdown bluetooth, yet the process remains alive and apparently can only be killed directly. Reproducible: Always
1) Please post your `emerge --info net-wireless/bluez' output. 2) Do the system logs record anything seemingly relevant?
Created attachment 291759 [details] emerge --info bluez
2) dmesg reports nothing.
Why should this be reported in dmesg? So you didn't check your syslogs?
This is "normal" -> that init.d script is only there to prevent a bug in udev that requires udevadm trigger to be run to get bluetooth device detected at boot time. But upstream wants us to let bluetoothd die on its own and not kill it with init script (you can check other distributions init scripts and see their stop function) Anyway, I think mgorny talked me sometime ago about some problems with this initscript with systemd, then, when I have time, I will probably try to kill init script (probably leaving a "rfcomm" one) and move udevadm trigger stuff directly to udev rule
*** Bug 396403 has been marked as a duplicate of this bug. ***
*bluez-4.97-r1 (31 Dec 2011) *bluez-4.97 (31 Dec 2011) 31 Dec 2011; Pacho Ramos <pacho@gentoo.org> +files/bluez-4.67-udev.script, -bluez-4.96-r2.ebuild, +bluez-4.97.ebuild, +bluez-4.97-r1.ebuild, +files/rfcomm-conf.d, +files/rfcomm-init.d: Version bump that also includes IMPORTANT changes: - old-daemons were dropped because they are poorly maintained and I am unable to test them. Also have some problems and look to not work at all in default setups (bug #381355 by Agostino Sarubbo and Rafał Mużyło). If you think you still need some of them, please open a new bug report explaining your needs to let us find a replacement or, if none is available, readd only needed old daemons. - 'bluetooth' init.d script has been completely removed as it was only calling "udevadm trigger --subsystem-match=bluetooth --action=add" at startup. This instruction is now called directly by /lib/udev/bluetooth.sh (the one that was previously calling init.d script and causing problems on systemd setups as reported by mgorny and others (bug #396403), this should also solve bug #389531. Due this change, it's possible that you will start to see how your bluetooth device is not properly detected just after booting if not manually running "udevadm trigger --subsystem-match=bluetooth --action=add", if this is your case, please report a bug to readd a bluetooth init.d script for that (even without getting it automatically started by udev to not hurt systemd users). - Because of previous change, 'rfcomm' part of old bluetooth init.d script has been moved to its own script under /etc/init.d and conf.d. - Due bug 392879 (by Otamay) I have rethink the way some plugins were being installed or not to simply always build and install them. This adds no additional dependencies, also simplifies ebuild preventing it from growing forever with a lot of USE flags and, probably the most important one, makes bluez to simply support and work with more devices. Also remove old.
