hid2hci is a one-shot application that switches HCI proxy dongles (as found in Macs, or in Logitech USB dongles) to HCI mode from their original HID mode. As we don't have the specs for those devices, we can't get information from the devices as to which Bluetooth devices would get connected, or their properties. So iMacs for example will end up with working Bluetooth, but no keyboard or mouse. So hid2hci should only be enabled on machines that have builtin keyboard/mouse, such as MacBooks, Powerbooks and iBooks.
If possible, it's better to start hid2hci only if there's no bluetooth mouse/keyboard that is already connected in HID mode. Can it be detected? You don't even need HAL for that probably. Otherwise, it wouldn't work for people that use bluetooth mice/keyboards with mac notebooks (because they are more convenient than builtin ones). I have a powerbook, and I always use an external mouse and keyboard unless I'm mobile. Fortunately mine are USB.
(In reply to comment #1) > If possible, it's better to start hid2hci only if there's no bluetooth > mouse/keyboard that is already connected in HID mode. Can it be detected? You > don't even need HAL for that probably. It can be detected, but it requires specs we don't have to implement this functionality. If we had the docs, we wouldn't be having this conversation :) > Otherwise, it wouldn't work for people that use bluetooth mice/keyboards with > mac notebooks (because they are more convenient than builtin ones). I have a > powerbook, and I always use an external mouse and keyboard unless I'm mobile. > Fortunately mine are USB. People can still enable it by hand, that's not going away.
> It can be detected, but it requires specs we don't have to implement this > functionality. If we had the docs, we wouldn't be having this conversation :) Maybe someone with a USB sniffer software on Windows can find out how it's done there?
Based on the date this bug was created, it appears to have been reported during the development of Fedora 8. In order to refocus our efforts as a project we are changing the version of this bug to '8'. If this bug still exists in rawhide, please change the version back to rawhide. (If you're unable to change the bug's version, add a comment to the bug and someone will change it for you.) Thanks for your help and we apologize for the interruption. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Oh yeah, the problem still exists in Fedora 9 Beta. I can't change the version back though.
Removing from the F9 target, not going to happen.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Another option is to make the switch only if there's another keyboard/mouse already connected - probably a small helper app should make that check.
Are you still running Fedora 9, or have you upgraded to 10 or Rawhide? In either case, can you let us know whether the issue is still happening, and give the current version of the HAL packages you're using? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Yes, read the bug.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Have you tried with the latest hal package in Fedora 11 or tried Rawhide? In either case, can you let us know whether the issue is still happening, and give the current version of the HAL packages you're using? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
In F12 bluetooth seems to just work by default for me. Not sure if this means the original problem is resolved though. Bastien?
Due to lack of response from original bug reporter I am closing this bug as CLOSED INSUFFICIENT_DATA. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers