I just bought a Logitech Bluetooth mouse (Mx900) which use bluetooth
for its wireless service and the mouse batterycharger also functions
as a bluetooth hub. However to make this mouse work on my Fedora
install having the 'Bluetooth services' enabled is not enough. I have
to run the command 'hid2hci' and 'hidd --server' before the mouse
I discussed the issue briefly with Edd Dumbill of gnome-bluetooth and
xml fame. He said that the two command above where run automatically
on a Debian system and that there wasn't really much of a reason not
to do so as it maximized making things 'just work'.
I hope the Red Hat/Fedora bluetooth service can be updated to do this
echo HID2HCI_ENABLE=true >> /etc/sysconfig/bluetooth
echo HIDDARGS=\"--server --search\" >> /etc/sysconfig/hidd
/sbin/chkconfig --level 345 hidd on
If that doesn't work, tell me about the failure.
If it does, then I suppose the best thing to do is refile a bug
against kudzu or the installer. Or suggest better ways that I could
autodetect the need to do these things.
Ok, I tested a lot around this now and here is what I found.
HIDHCI_ENABLE was already set to TRUE.
For HIDDARGS I noticed something peculiar. If I just use the --server
option things work fine. But if I have the --search option added then
a few things happen. First of all I think the hidd process dies at
some point as I am not able to stop the hidd service without getting
failed when it is on. Secondly it do seem to do something with my
mouse as it basically stops working until I take out the batteries
from it to reset it. But as I said, just having '--server' as the
option makes everything work fine.
It looks like '--server --search' was wrong; sorry. Those are mutually
exclusive options. As you observed, you only want '--server'. I'll fix
the shipped config file.
When looking at #157971 comment 15, I think there's still the problem that
hidd startup script isn't linked to any runlevels in FC4T3, and chkconfig
--add is manually needed...
I don't think we should necessarily be running hidd by default in all cases. The
installed should probably enable it only if it's needed. The installer needs to
learn about Bluetooth keyboard/mouse anyway.