** Also affects: ofono (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: ofono (Ubuntu RTM)
Status: New => Fix Committed
** Changed in: ofono (Ubuntu RTM)
Importance: Undecided => High
** Changed in: ofono (Ubuntu RTM)
Assignee: (unassigned) =>
Here's the associated pull-request ( currently under-review ):
https://github.com/rilmodem/ofono/pull/214
** Changed in: ofono (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
@Simon
Regarding the battery mismatch, the HFP 1.6 specification ( section
4.33.2 AT Capabilities Re-Used from GSM 07.07 and 3GPP 27.007 )
documents that the battery level is indicated by an integer between 0
and 5. For a battery percentage of 1 or less, we indicate 0. Above
1%, we divide by
** Summary changed:
- Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ
Aquaris 4.5
+ Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ
Aquaris 4.5
--
You received this bug notification because you are a member of Kernel
Packages, which
** Attachment added: "krillin-btctl.out"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+attachment/4536395/+files/krillin-btctl.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Attachment added: "krillin-syslog"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+attachment/4536396/+files/krillin-syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
While debugging some re-factoring work on the ofono upower plugin, I
noticed that I wasn't able to answer or terminate calls using my Jawbone
ERA headset. I bought this headset last year, and although it's an
older model, it's spec sheet states that it supports HSP 1.1, and
** Attachment added: "krillin-hciconfig.out"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+attachment/4536394/+files/krillin-hciconfig.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Attachment added: "ofono.override"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+attachment/4536397/+files/ofono.override
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
@Uranicus
Thanks for the heads-up re: battery status. The plugin that handles
battery status currently doesn't properly handle dual-SIM. It's on our
list to resolve before OTA9 is released.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I just flashed my mako to the same image as Willem ( rc-proposed/331 )
and couldn't reproduce the problem. After a fresh flash, I rebooted
the device multiple times with BT enabled, after each reboot, BT was
still enabled. I rebooted ten times, and wasn't able to reproduce...
I also verified
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1531515
Title:
Bluetooth cannot be enabled on Ubuntu Touch rc-proposed
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
--
You received this bug notification because you are a member of Kernel
Packages,
Re-tested to check that initiating the connection from the phone ( ie.
by doing a fresh pairing ) doesn't make a difference.
Nothing has been upgraded on the phone, same image used as when the bug
was reported. No difference after connecting from the phone; syslog
attached.
** Attachment
Re-tested with the last stable image ( ie. bluez4 userspace ) on
krillin, and the headset functions works fine regardless of which side
initiates the connection.
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 24
device name: krillin
channel: ubuntu-touch/stable/ubuntu
last
** Tags added: bluetooth-ota9
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1527354
Title:
[Jawbone ERA] HFP features not working with Bluez5
Status in bluez package in Ubuntu:
New
I'm able to reproduce it every time on a krillin running OTA8.5 ( bluez4
userspace ):
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 26
device name: mako
channel: ubuntu-touch/stable/ubuntu
last update: 2015-12-22 23:02:17
version version: 26
version ubuntu: 20151210
version
@Simon
It works fine with my iPhone6, and has worked properly before with
Ubuntu...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1527354
Title:
[Jawbone ERA] HFP features not working
@Simon
Pretty sure my results reported in comment #11 were using the silo, so
5.37 doesn't resolve the problem.
I just re-tested on arale ( rc-proposed, 350 ) and still see the same
behavior on the initial connect of the headset. Unfortunately, I can't
seem to get the headset to work at all now
@Matthias
So what you're saying is that you see the correct battery level
displayed in your car the first time after you connect the phone and
car, and then after you restart the car, the battery level is just shown
as full? Once this happens, does the battery level displayed ever change
or does
** Also affects: ofono (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ofono (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: ofono (Ubuntu)
Status: New => Confirmed
** Changed in: ofono (Ubuntu RTM)
Status: New => In Progress
**
** Changed in: ofono (Ubuntu RTM)
Status: In Progress => Fix Committed
** Changed in: ofono (Ubuntu RTM)
Importance: Undecided => Critical
** Changed in: ofono (Ubuntu)
Importance: Undecided => High
** Changed in: ofono (Ubuntu)
Importance: High => Critical
** Changed in: ofono
Re-tested on krillin, rc-proposed #231. Same result, my Jawbone only
works as a headset. Same result on arale ( rc-proposed, #220 ). On
mako ( rc-proposed, #331 ) I couldn't even get the headset function to
work.
--
You received this bug notification because you are a member of Kernel
@Uranicus
Right now I think we have enough information. We'll let you know if we
need more...
Hopefully we can get this squared away for OTA10.
Thanks for your patience...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
Based on comment #8 and discussion with the product team, I've changed
the ofono tasks back to 'Confirmed' as it seems there's more work to do.
** Changed in: ofono (Ubuntu)
Status: In Progress => Confirmed
** Changed in: ofono (Ubuntu RTM)
Status: In Progress => Confirmed
--
** Changed in: ofono (Ubuntu RTM)
Status: Fix Released => In Progress
** Changed in: ofono (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Branch linked: lp:~bluetooth/bluez/new-rel-5-37-plus-touch-xenial-
sync
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1527354
Title:
[Jawbone ERA] HFP features not working with
Re-tested on arale ( rc-proposed - 258 ) with bluez 5.37 ( from silo 39
) and I'm able to terminate a call from the headset.
Re-tested on krillin ( rc-proposed - 419 ) with bluez 5.37 ( same silo )
and I'm also able to terminate the call from the headset.
Note - I also installed pulseaudio from
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
bluetoothd crash with BTLE keyboard
Status in bluez package
** Description changed:
Trying to pair this device and bluetoothd crashed on my Wily laptop and
the N4 running latest proposed
build number: 107
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu-pd
last update: 2016-01-07 11:30:20
version version: 107
version ubuntu:
A couple of updates...
- I've verified that the keyboard is indeed a low-energy device.
- I'm able to see the device on my MacAir running 15.10 + the latest
5.37 bluez packages both in the indicator, and via bluetoothctl
- I cannot successfully pair with the device from the indicator or
Also, I have yet to be able to reproduce the crash...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
bluetoothd crash with BTLE keyboard
Status in bluez package in
** Summary changed:
- bluetoothd crash with BTLE keyboard
+ Can't connect Logitech Living Room Keyboard [LE]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1531925
Title:
Can't connect
** Description changed:
- Trying to pair this device and bluetoothd crashed on my Wily laptop and
- the N4 running latest proposed
+ Cannot connect a Logitech Illuminated Living Room keyboard to a device
+ running bluez5. There are two versions of the keyboard, a unifying
+ receiver version, and
Added a task for ubuntu-system-settings as LE devices aren't considered
at all by Bluetooth settings.
** Description changed:
Cannot connect a Logitech Illuminated Living Room keyboard to a device
running bluez5. There are two versions of the keyboard, a unifying
receiver version, and a
OK, so I guess I was wrong about pairing working with my Ubuntu desktops
( both running 5.37 ), although I'm pretty sure this worked for me
before. Maybe I was running bluez 5.36 when I tested?
Here's a btmon trace of wily running bluez 5.37 on a mid '13 macair. I
get prompted to view the PIN
Note, I forgot to mention in the previous comment that on xenial
desktop, the PIN wasn't displayed in settings.
Finally, here's the trace from my krillin, running rc-proposed/bq-
aquaris.en #270 + bluez 5.37. Same result as the original bug
description.
** Attachment added: "btmon trace"
And here's the trace for my xenial desktop running on a Thinkpad 410s.
** Attachment added: "btmon trace"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4593245/+files/xenial-desktop.cap
--
You received this bug notification because you are a member of
(Ubuntu)
Assignee: Tony Espy (awe) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1387949
Title:
power cycling Emerson EM229 headset caused phone to reb
Our wrapper scripts for bluez ( bluetoothd ) and obexd are currently
copying DBus configuration files before starting the service. This was
done as snappy had no way to allow a framework type snap such as bluez
or network-manager a way to install a DBus configuration file.
** Branch linked:
@Jamie
Thanks for the comment... I'll work on re-vising the snapcraft.yaml
and will follow-up with zyga for details on the new snappy dbus
interface. Hopefully it allows us to do all that the standard DBus conf
file allows.
--
You received this bug notification because you are a member of
I see those error messages quite frequently on touch devices running
Bluez5 as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1557298
Title:
[Xenial][Bluez5] Low Energy Keyboard
** Changed in: bluez (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: canonical-devices-system-image
Status: Confirmed => Incomplete
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Selene Scriven (toykeeper)
--
You received this bug notification because you
** Attachment added: "dbus log from krillin"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591780/+files/dbus.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Description changed:
Connecting to the latest generation Apple BT keyboard ( the one with the
USB port & no batteries ) fails on an Ubuntu Touch device, as when you
press the "Connect" button on the device page, a dialog titled
"Bluetooth Pairing Request" is displayed, with the
Re-tested on krillin ( rc-proposed/bq-aquaris.en / 270 ), this time with
bluez 5.37 installed from the silo.
@Simon, how could this not be a system settings app failure? As I
pointed out in my description, pairing this keyboard works fine with
every other device I tried, including two Ubuntu
** Attachment added: "system settings log from krillin"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591779/+files/application-legacy-ubuntu-system-settings-.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
Note, it turns out that if the headset initiates the connection, then
the HFP features work. It's only when the connection is initiated from
the phone ( ie. when first pairing the device ) that the HFP features
fail.
To reproduce easily:
1. Goto to settings & forget the device if previously
@Simon
Re: comment #6, when I paired the keyboard with my Ubuntu laptops,
neither prompted me at all; the keyboard silently paired and was usable.
That said, I'll re-test this afternoon and get you the HCI dump from the
phone.
--
You received this bug notification because you are a member of
I just ran an additional five cycles of the testing described in my
previous comment with no failures.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762672
Title:
TPM intermittently
Tested the latest OEM kernel from -proposed on a Dell Edge Gateway 3000
running Ubuntu Server 18.04 LTS:
# rmadison linux-image-oem | grep bionic-proposed
linux-image-oem | 4.15.0.1035.40 | bionic-proposed | amd64
# dpkg -l | grep linux-image-oem
ii linux-image-oem
@Tyler
So it looks like we landed this just in time for the new SRU cycle,
which means we're looking at a tentative release to proposed on Mar 25.
Does that sound right? If so, I may check with Anthony to see if there's
a possibility that linux-oem could possibly re-spin and release
earlier...
** Summary changed:
- TPM on Dell XPS 13 stopped working after upgrade to 18.04
+ TPM intermittently fails after cold-boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762672
Title:
** Description changed:
- [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
- [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
- [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
- [0.895424] tpm tpm0: A TPM error (2314)
I've run 10 cold boots on the gateway mentioned in my previous comment,
and in each case after issuing a tpm2_startup clear command, I've been
able to query the NVLIST of the TPM. So the back-ported patch appears to
be working as advertised.
--
You received this bug notification because you are
@Tyler I've tested your kernel on a Dell Edge Gateway 3000 which was
showing the same TPM selftest log messages as originally described in
this bug. When cold-booted with your kernel I only see the following
messages now:
14:57:44 [0.00] ACPI: TPM2 0x76D537C8 34 (v03 Tpm2Tabl
@Khaled
Just curious as to why this is now FixCommitted? Has Tyler's back-port
landed in git for the next OEM and/or mainline kernel SRU release?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
snappy-hwe-snaps is a project used to track work related to system stack
snaps published by Canonical. Your bug most likely has to do with the
bluez (or related) Debian package from the Ubuntu archive.
** Project changed: snappy-hwe-snaps => bluez
** Project changed: bluez => bluez (Ubuntu)
--
Public bug reported:
A customer recently reported that 'sudo docker run hello-world' fails on
a pi3 or pi4 running UC18. Looking at the journal, the failure appears
to be caused by an apparmor denial related docker's overlay2 storage
driver. I've tried both the unified and the Pi3 specific UC18
59 matches
Mail list logo
