HP Bluetooth Printer Pairs but Stays Disconnected

Bug #1787304 reported by Free Beachler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I have an HP Deskjet 460 with BT module. This printer was working via Bluetooth in Ubuntu 16.04, but now fails to connect in Ubuntu 18.04.

In Ubuntu 16.04 I was able to use this doc to setup the printer: https://help.ubuntu.com/community/BluetoothPrinterSetup. However, this doc is now outdated for Ubuntu 18.04 since "hidd" is unavailable.

I've tried the info contained in these links to no avail:
- https://askubuntu.com/questions/1020257/bluez5-cannot-connect-to-a-paired-bluetooth-device-on-ubuntu-17-10
https://askubuntu.com/questions/1036195/bluetooth-doesnt-work-after-resuming-from-sleep-ubuntu-18-04-lts?rq=1
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748565
- https://askubuntu.com/questions/1037370/ubuntu-18-04-bluetooth-device-disconnects-right-after-connect-on-lenovo-p50

* I did try to "update bluez to >=5.28.2"
* I did try to "restarting bluetooth service"
* I did not try "removing btusb module"

Further advice in the above links did not help.

In 18.04 I can remove the device using the Settings->Bluetooth UI. Then the Deskjet 460 S/N XXXXXXX appears as "Not Set Up". Then I can double-click on the device, and it briefly shows "Connected", then "Disconnected". Now the device is in the Settings->Bluetooth UI, and when I double click the device it shows "Connection Off", Paired Yes, Type Printer, and the MAC address. I'm unable to change the "Connection Off" setting via the UI.

From bluetoothctl:
> remove 00:0C:78:51:44:D6
[DEL] Device 00:0C:78:51:44:D6 Deskjet 460 S/N XXXXXXXXXX
Device has been removed
[NEW] Device 00:0C:78:51:44:D6 Deskjet 460 S/N XXXXXXXXXX
> trust 00:0C:78:51:44:D6
[CHG] Device 00:0C:78:51:44:D6 Trusted: yes
Changing 00:0C:78:51:44:D6 trust succeeded
> pair 00:0C:78:51:44:D6
Attempting to pair with 00:0C:78:51:44:D6
[CHG] Device 00:0C:78:51:44:D6 Connected: yes
[CHG] Device 00:0C:78:51:44:D6 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 00:0C:78:51:44:D6 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 00:0C:78:51:44:D6 UUIDs: 0000111b-0000-1000-8000-00805f9b34fb
[CHG] Device 00:0C:78:51:44:D6 UUIDs: 00001123-0000-1000-8000-00805f9b34fb
[CHG] Device 00:0C:78:51:44:D6 UUIDs: 00001126-0000-1000-8000-00805f9b34fb
[CHG] Device 00:0C:78:51:44:D6 ServicesResolved: yes
[CHG] Device 00:0C:78:51:44:D6 Paired: yes
Pairing successful
[CHG] Device 00:0C:78:51:44:D6 ServicesResolved: no
[CHG] Device 00:0C:78:51:44:D6 Connected: no
> connect 00:0C:78:51:44:D6
Attempting to connect to 00:0C:78:51:44:D6
Failed to connect: org.bluez.Error.Failed

dmesg -w from the above bluetoothctl session:
[47676.543096] Bluetooth: hci0: last event is not cmd complete (0x0f)
[47692.543107] Bluetooth: hci0: last event is not cmd complete (0x0f)
[47711.542175] Bluetooth: hci0: last event is not cmd complete (0x0f)
[47727.544169] Bluetooth: hci0: last event is not cmd complete (0x0f)

Machine: ASUS_GL551JM.

Description: Ubuntu 18.04.1 LTS
Release: 18.04

Why did this break?
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: michelle 3174 F.... pulseaudio
 /dev/snd/controlC0: michelle 3174 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2f8fccbc-e235-4e8b-9ea2-c30c8b90e7b1
InstallationDate: Installed on 2016-10-18 (666 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK COMPUTER INC. G551JM
Package: linux (not installed)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash pcie_aspm=force acpi_os=Windows acpi_backlight=native vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic N/A
 linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-32-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-08-15 (1 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G551JM.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G551JM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG551JM.204:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnG551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G551JM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1787304

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: bionic
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Free Beachler (tenacious) wrote :

Thanks @Joseph, this issue started happening after an upgrade 16.04 -> 18.04 via CLI. Prior to upgrade I was on the latest 16.04 kernel as I had applied automatic updates constantly and restarted recently. Sorry, as I don't recall the kernel version.

Yes, I can try to test against the latest upstream kernel when time permits.

Revision history for this message
Free Beachler (tenacious) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Free Beachler (tenacious) wrote : CRDA.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : IwConfig.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : Lspci.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : Lsusb.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : ProcModules.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : PulseList.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : RfKill.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : UdevDb.txt

apport information

Revision history for this message
Free Beachler (tenacious) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Free Beachler (tenacious) wrote :
Revision history for this message
Free Beachler (tenacious) wrote :
Brad Figg (brad-figg)
tags: added: cscc
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.