Ubuntu
bluez package

BlueZ crashing when connecting input channel to a keyboard

Bug #1400827 reported by Michael Zanetti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
Unassigned
Canonical System Image ww05-2015
bluez (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
bluez (Ubuntu RTM)
Fix Released
High
Mathieu Trudel-Lapierre

Bug Description

On the phone, pairing a keyboard makes BlueZ crash when connecting the input channel (either by calling org.bluez.Input.Connect() on D-Bus or by pressing some keys on the keyboard to make the keyboard open the channel.

In order to pair a keyboard with an Ubuntu phone, you need to either apply this branch to ubuntu-system-settings [1] or do it manually with bluez-simple-agent and dbus-send/qdbus.

[1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input

Related branches

lp:ubuntu/vivid/bluez
Revision history for this message
kevin gunn (kgunn72) wrote :

in order to help set priority, we're hoping to have this functionality to support convergence demonstrations ~Feb 22015

Revision history for this message
kevin gunn (kgunn72) wrote :

dang it...that's 2015, not 22015....so few months, not 20,000 years+few months

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

It seems this was fixed on vivid during the latest upload for bluez. Was this bug reported against vivid or RTM?

Ricardo Salveti (rsalveti)
Changed in bluez (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael Zanetti (mzanetti) wrote :

Yes. Can connect fine to Nexus7 with vivid on it now.

Setting this to fixed.

Changed in bluez (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Michael Zanetti (mzanetti) wrote :

Actually no, sorry. I can connect a keyboard now sometimes. But it still crashes BlueZ most of the times which makes it a very unreliable experience.

Changed in bluez (Ubuntu):
status: Fix Released → New
Revision history for this message
Michael Zanetti (mzanetti) wrote :

Crash file from a vivid Nexus 7 with r63

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

This still looks like a bug that should have been "fixed" by bluez 4.101-0ubuntu21; could you please confirm that this is indeed the version of bluez that was installed, and running, on the system when you got the crash?

I'm saying "fixed", because it's been tested on some hardware, specifically for armhf and without adverse effects on amd64 or other architectures, but it doesn't mean it's necessary the proper, best solution on all hardware.

Revision history for this message
Michael Zanetti (mzanetti) wrote :

phablet@ubuntu-phablet:~$ apt-cache policy bluez
bluez:
  Installiert: 4.101-0ubuntu21
  Installationskandidat: 4.101-0ubuntu21
  Versionstabelle:
 *** 4.101-0ubuntu21 0
        500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages
        100 /var/lib/dpkg/status

Revision history for this message
Michael Zanetti (mzanetti) wrote :

Here's /var/lib/bluetooth/ when the crashing starts happening:

Mathieu Trudel-Lapierre (cyphermox)
Changed in bluez (Ubuntu):
status: New → In Progress
importance: Undecided → High
Changed in bluez (Ubuntu RTM):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Changed in bluez (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluez - 4.101-0ubuntu22

---------------
bluez (4.101-0ubuntu22) vivid; urgency=medium

  * debian/patches/fix_armhf_hcigetconninfo_free.patch: drop, fails in some
    cases to properly fix the issue.
  * debian/patches/fix_hcigetconninfo.patch: replaces the patch above; double
    the size of the memory requested to hold struct hci_conn_info; which
    should allow enough space for the kernel to write the connection data in
    all cases. (LP: #1400827)
 -- Mathieu Trudel-Lapierre <email address hidden> Wed, 14 Jan 2015 11:26:22 -0500

Changed in bluez (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

need for convergence work

Changed in canonical-devices-system-image:
importance: Undecided → High
milestone: none → ww05-2015
status: New → Confirmed
Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluez - 4.101-0ubuntu22rtm1

---------------
bluez (4.101-0ubuntu22rtm1) 14.09; urgency=medium

  * Sync ubuntu 4.101-0ubuntu22 to RTM.
 -- Mathieu Trudel-Lapierre <email address hidden> Fri, 16 Jan 2015 11:10:23 -0500

Changed in bluez (Ubuntu RTM):
status: In Progress → Fix Released
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.