© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Okay, so I forgot to mention something: I had the module "btusb" blacklisted by default. The reason was mostly to save some power when I don't use bluetooth. I wonder if those Fedora users did the same.
Anyway, now I removed "btusb" from blacklist and rebooted. And now it all works !
This seems to make sense because I suspect that whenever the bluetooth service is started at boot time, it needs btusb to be loaded already. So if you load the module afterwards, you need to restart the service.
At this point, if this is by design, feel free to close as the problem is solved for me.
-------
My bluetooth adapter is built-in, so far so good.
But what happens for people who have bluetooth USB dongles ? Would btusb only load later once the dongle is plugged in ? If that's the case, then the problem I describe *might* happen for said users who might need to restart the bluetooth service.
Now this is marked as regression, it used to work with previous bluez versions. So not sure if this is something to be fixed upstream or whether this slight change of behavior / expectation is by design.