I read the rationale for removing /etc/init.d/bluetooth in net-wireless/bluez-4.97-r1, but I must admit that I don't quite understand it... In any case, on the next reboot after the update, I lost both my keyboard and my mouse... A less than ideal scenario. I suppose I may be the first to have found a wired keyboard, otherwise probably a lot of other inconvenienced users would have reported this already... (-; Reproducible: Always
I am aware of the problem, but will wait a bit for bug 397701 For now, running "udevadm trigger" to your local.start should workaround this problem
(In reply to comment #1) > I am aware of the problem, but will wait a bit for bug 397701 > > For now, running "udevadm trigger" to your local.start should workaround this > problem This _almost_ worked. I also had to start DBUS before (and stop it after), as this version of bluetoothd seems NOT to *start* without DBUS running (but it keeps working even with DBUS stopped)... Here's my /etc/local.d/bt.start: ---- /etc/init.d/dbus start udevadm trigger --subsystem-match=bluetooth /etc/init.d/dbus stop ----
+*bluez-4.97-r3 (09 Jan 2012) +*bluez-4.97-r2 (09 Jan 2012) + + 09 Jan 2012; Pacho Ramos <pacho@gentoo.org> +bluez-4.97-r2.ebuild, + +bluez-4.97-r3.ebuild, +files/bluetooth-init.d-r1, -bluez-4.97-r1.ebuild, + -bluez-4.97.ebuild: + Reintroduce a bluetooth init.d script to trigger bluetooth devices after dbus + is started because, as talked with WilliamH, udev-postmount will be removed in + the near future due upstream no longer detecting failed triggers at early + boot. This should also solve bug 397673 by a.m. Drop old. +