snum, is this an existing installation where bluetooth was previously working or a new one? Also, which arch are your running, stable or ~?

I ask this because there is an issue with the latest version of bluez in portage, and if you're running ~ then you may want to consider masking net-wireless/bluez-4.101 until things get resolved. See bug https://bugs.gentoo.org/show_bug.cgi?id=423513

My previously working bluetooth installation began failing last week. I was getting the exact same output as you when I queried my device. I thought it was related to the recent policykit updates. It turns out that the latest version of bluez no longer starts a daemon that was previously handled by udev. Arch Linux has resolved this by patching bluez. Our devs unfortunately, have yet to even recognize the existence of this bug as it's still listed as "unconfirmed" in bugzilla.

If you downgrade to the previous version of bluez, your device should work as intended.

If the downgrade solves your problem, please chime in on the above mentioned bug report. We need to get the devs to solve this and the more users that post with this issue the more likely it will be recognized and resolved in a timely manner.

Now if you're running stable and this is a new installation, then the most likely culprit is that you need to install the firmware files to have bluez initialize your device. Try installing net-wireless/bluez-firmware.

One of these solutions will likely have you up and running in no time.

Thank you!
I mask 'wireless/bluez-4.101' package and install previous package version (wireless/bluez-4.99) and bluettoth started to work as before.
I add comment on bugs.gentoo.org and believe problem will fixed in bluez-4.101 too.
Now problem with bluetooth fixed, but the mouse does not work(did not work before).
I have mouse Raser Orochi.
I add this mouse in devices(Bluetooth settings in Gnome).
Try to use and nothing happens(only mouse wheel using change connection status from On to Off).
Mouse setting:
Paired: No
Type: Mouse
Adress: 00:02:76:32:0D:63

Odysseus wrote:

snum, is this an existing installation where bluetooth was previously working or a new one? Also, which arch are your running, stable or ~?

I ask this because there is an issue with the latest version of bluez in portage, and if you're running ~ then you may want to consider masking net-wireless/bluez-4.101 until things get resolved. See bug https://bugs.gentoo.org/show_bug.cgi?id=423513

My previously working bluetooth installation began failing last week. I was getting the exact same output as you when I queried my device. I thought it was related to the recent policykit updates. It turns out that the latest version of bluez no longer starts a daemon that was previously handled by udev. Arch Linux has resolved this by patching bluez. Our devs unfortunately, have yet to even recognize the existence of this bug as it's still listed as "unconfirmed" in bugzilla.

If you downgrade to the previous version of bluez, your device should work as intended.

If the downgrade solves your problem, please chime in on the above mentioned bug report. We need to get the devs to solve this and the more users that post with this issue the more likely it will be recognized and resolved in a timely manner.

Now if you're running stable and this is a new installation, then the most likely culprit is that you need to install the firmware files to have bluez initialize your device. Try installing net-wireless/bluez-firmware.

One of these solutions will likely have you up and running in no time.

After a long time of error-free bluetooth operation, this problem caught up with me. too. The real oddity, and one that I think is at the core of the initial problem, is that

Code:

Bus 004 Device 002: ID 03f0:231d Hewlett-Packard 4 GB Flash Drive

is actually the bluetooth module in its uninitialized form. Once the driver gets loaded, it changes its id from 231d to 241d. But since it is believed to be a flash drive, that driver never gets loaded, apparently. I am positive that lsusb showed a bluetooth device in the past.