** Tags added: bluez-touch
** Changed in: bluez (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521737
Title:
Cannot enable bluetooth
To manage n
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521737
Title:
Cannot enable bluetooth
To manage notificatio
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Milestone: None => ww02-2016
--
You received this bug notification because you
** Changed in: bluez (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521737
Title:
Cannot enable bluetooth
To manage notifications about this bug go to:
ht
Have a fix for the crash. Uploading a new bluez package to silo 9.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521737
Title:
Cannot enable bluetooth
To manage notifications about this bug go to:
Examined the crash file I got from Pat:
#0 strlen () at ../sysdeps/arm/armv6t2/strlen.S:85
85 ../sysdeps/arm/armv6t2/strlen.S: No such file or directory.
(gdb) bt
#0 strlen () at ../sysdeps/arm/armv6t2/strlen.S:85
#1 0xb6f13ebc in avrcp_handle_media_player_list (session=0xb8f339c0,
se
It would be awesome if you get the crash file from
/var/crash/_usr_lib_bluetooth_bluetoothd.0.crash and could send it to
me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521737
Title:
Cannot enabl
@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-a
Log reports
Dec 1 09:25:00 ubuntu-phablet bluetoothd[744]: Not enough free handles to
register service
so we may have new FH leaks
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Pat McGo
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1521737/+attachment/4528176/+files/syslog
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Description changed:
MX4 running propsoed 181 with debug enabled kernel
Pai
10 matches
Mail list logo
