Ubuntu
blueman package

Bluetooth: hci0: Opcode 0x 401 failed: -16 when trying to connect to Bluetooth speaker

Bug #2015702 reported by Bric
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hello,
I recently format my Slimbook ProX 14. I had Ubuntu 22.04.2 LTS and I reinstall the same version to have a fresh install.
I have a bluetooth speaker (UE BOOM 2), since the reinstallation, I can't connect to it. I have the error in /var/log/kern.log:
Apr 9 21:14:33 me-pc kernel: [42022.714261] Bluetooth: hci0: Opcode 0x 401 failed: -16
Apr 9 21:14:37 me-pc kernel: [42027.157322] Bluetooth: hci0: Opcode 0x 401 failed: -16

I can see correctly the speaker in the list of available devices.

I also tried to install blueman-manager but the problem is the same:

Apr 9 21:18:58 me-pc <email address hidden>[2678]: unable to update icon for blueman
Apr 9 21:18:59 me-pc <email address hidden>[2678]: unable to update icon for blueman
Apr 9 21:19:00 me-pc blueman-manager.desktop[52105]: blueman-manager 21.19.00 WARNING ManagerDeviceList:341 _monitor_power_levels: Failed to get power levels, probably a LE device.
Apr 9 21:19:00 me-pc blueman-manager.desktop[52105]: blueman-manager 21.19.00 ERROR Manager:213 error_handler: org.bluez.Error.ConnectionAttemptFailed Page Timeout
Apr 9 21:19:00 me-pc blueman-manager.desktop[52105]: Traceback (most recent call last):
Apr 9 21:19:00 me-pc blueman-manager.desktop[52105]: File "/usr/lib/python3/dist-packages/blueman/bluez/Base.py", line 78, in callback
Apr 9 21:19:00 me-pc blueman-manager.desktop[52105]: value = proxy.call_finish(result).unpack()
Apr 9 21:19:00 me-pc blueman-manager.desktop[52105]: gi.repository.GLib.GError: g-io-error-quark: GDBus.Error:org.bluez.Error.ConnectionAttemptFailed: Page Timeout (36)
Apr 9 21:19:04 me-pc <email address hidden>[2678]: unable to update icon for blueman
Apr 9 21:19:06 me-pc kernel: [42295.519670] Bluetooth: hci0: Opcode 0x 401 failed: -16

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2015702/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Bric (bricrukappallou-8601) wrote :

Hello,
It is my first bug report. Sorry if not in the good category. Indeed, it could be a general bug. Please, feel free to move it in the good section.

Brian Murray (brian-murray)
affects: ubuntu → blueman (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blueman (Ubuntu):
status: New → Confirmed
Revision history for this message
lhotari (lartsa) wrote (last edit ):

I had a similar issue with Nothing Ear(2) headphones that there would be the error message "Bluetooth: hci0: Opcode 0x 401 failed: -16". This error message would happen with Intel AX200 as the bluetooth controller (Dell XPS 15 7590).
The workaround for the problem is to disable Bluetooth LE while pairing the device. Here's how to do that: https://askubuntu.com/a/833323 (temporarily add "ControllerMode = bredr" to /etc/bluetooth/main.conf).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.