Summary: | net-wireless/bluez-4.97-r1 - bluetooth keyboard/mouse stopped working with /etc/init.d/bluetooth missing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Another Mortal <a.m> |
Component: | [OLD] Unspecified | Assignee: | Tiziano Müller (RETIRED) <dev-zero> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kevinpoubelle, mobile+disabled, pacho, pda |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 397701 | ||
Bug Blocks: |
Description
Another Mortal
2012-01-04 19:22:12 UTC
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. + |