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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1400827 Title: BlueZ crashing when connecting input channel to a keyboard Status in bluez package in Ubuntu: New 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1400827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
