can't pair bluetooth headphones failed to add device

Bug #1896830 reported by alexander krivusha
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

can't pair bluetooth headphones failed to add device.
during pairing error in blueman-applet - "Failed to add device".
Adress D8:AF:F1:A9:AF:73
Name RP-HTX80B
Class 0x240404
Adapter /org/bluez/hci0
....

ent.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=6955 label="snap.chromium.chromium" peer_pid=1984 peer_label="unconfined"
Sep 23 22:29:43 alex-MS-7A37 dbus-daemon[1654]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=6955 label="snap.chromium.chromium" peer_pid=1984 peer_label="unconfined"
Sep 23 22:30:01 alex-MS-7A37 bluetoothd[67977]: D8:AF:F1:A9:AF:73: error updating services: Connection timed out (110)
Sep 23 22:31:16 alex-MS-7A37 kernel: [ 1830.694799] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
Sep 23 22:31:16 alex-MS-7A37 kernel: [ 1830.694803] debugfs: File 'le_max_key_size' in directory 'hci0' already present!
Sep 23 22:31:16 alex-MS-7A37 kernel: [ 1830.694805] debugfs: File 'force_bredr_smp' in directory 'hci0' already present!
Sep 23 22:32:17 alex-MS-7A37 bluetoothd[67977]: D8:AF:F1:A9:AF:73: error updating services: Connection timed out (110)
Sep 23 22:32:17 alex-MS-7A37 dbus-daemon[1654]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=6955 label="snap.chromium.chromium" peer_pid=1984 peer_label="unconfined"
Sep 23 22:32:17 alex-MS-7A37 dbus-daemon[1654]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/PowerManagement/Inhibit" interface="org.freedesktop.PowerManagement.Inhibit" member="Inhibit" mask="send" name="org.freedesktop.PowerManagement" pid=6955 label="snap.chromium.chromium" peer_pid=1984 peer_label="unconfined"
Sep 23 22:45:22 alex-MS-7A37 obexd[2078]: Unable to find service record
Sep 23 22:45:39 alex-MS-7A37 bluetoothd[67977]: D8:AF:F1:A9:AF:73: error updating services: Host is down (112)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Sep 23 22:37:02 2020
InstallCmdLine: file=/cdrom/preseed/kubuntu.seed maybe-ubiquity initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-09-05 (18 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: ubiquity
Symptom: installer
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
alexander krivusha (stirchshade) wrote :
affects: ubuntu → ubiquity (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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