@Pat: No that is not a file descriptor leak. That is just an internal handle not related to any file descriptors to store GATT related attributes. This due to some unconverted profiles after API/infrastructures changes and known upstream. Ignore that.
Also ignore that there is no bluetooth-touch-arale job. That is not needed on arale and therefor doesn't exist. -- 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/1521737 Title: Cannot enable bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: MX4 running propsoed 181 with debug enabled kernel Paired to car and saw signal strength indicated Left car, renetered car and noticed not paried and BT disabled in the indicator tried to enable, 1 min later it resets to disabled Bluetoothd is no longer running there was a previous crash file in /var/crash see syslog attached /var/lib/urfkill/saved-states: [BLUETOOTH] soft=false prev-soft=false /var/log/upstart/bluetooth-touch.log start: Unknown job: bluetooth-touch-arale Reboot and bt is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521737/+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
