Bluetooth printing does not work

Bug #1080507 reported by Till Kamppeter on 2012-11-19
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)

Bug Description

I have applied the workaround of bug 1070770, running bluetoothd under valgrind to prevent it from crashing. See

After successfully connecting my Bluetooth keyboard I tried to connect with a Bluetooth printer, the Photosmart Premium C309g-m. To do so, the "bluetooth" CUPS backend needs to detect the printer. On a standard Intel-based computer I get

till@till:~$ /usr/lib/cups/backend/bluetooth
direct bluetooth://002655096A9C "Photosmart Premium C309g-m" "Photosmart Premium C309g-m (Bluetooth)"

On the Nexus 7 the same call of the bluetooth backend does not show any answer and never exits, probably hanging during the communication with the printer.

Using the bluez-tools on the Nexus 7 I get:

ubuntu@nexus7-pyongyangs:~$ bt-adapter -d

  Name: (null)
  Alias: 00-26-55-09-6A-9C
  Address: 00:26:55:09:6A:9C
  Icon: printer
  Class: 0x140680
  LegacyPairing: 0
  Paired: 0
  RSSI: -65

ubuntu@nexus7-pyongyangs:~$ sudo bt-device -c 00:26:55:09:6A:9C
[sudo] password for ubuntu:
Connecting to: 00:26:55:09:6A:9C
Agent registered
Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

The error message of the second command only showed up after waiting some seconds.

Changed in bluez (Ubuntu):
importance: Undecided → Medium
importance: Medium → High
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

An additional remark: THe attempt to connect to the printer via the "bt-device -c ..." command makes bluetoothd crash.

Revision history for this message
Chris Wayne (cwayne) wrote :

Just adding a note here that since Bluetooth is not yet officially working on the Nexus 7, I am going to wait to try and reproduce until we have an official fix. I'm a bit concerned about testing with such a workaround.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Chris, is this depending on a kernel fix or does it need an actual bluez stack update? Can you link the kernel bug if it's a kernel issue?

Triaging to importance Medium as suggested by Robert Park; I think bluetooth should remain as a fairly high priority since it affects the usefulness of the Nexus as a portable computer. Using bluetooth certainly beats lugging around countless cables for the tablet, and when using OTG you can't charge...

Changed in ubuntu-nexus7:
status: New → Confirmed
Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Ah, I meant this to remain at priority High :D

tags: added: mobile nexus7
Revision history for this message
Tony Espy (awe) wrote :

Updated the bluez task to WontFix, as this is an old image, with an unsupported version of bluez ( eg. 4.x ) and there's no plans to fix this.

Changed in bluez (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers