[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-03-28 Thread Tony Espy
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 fails after cold-boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [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) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-03-28 Thread Tony Espy
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   4.15.0.1035.40
  amd64OEM Linux kernel image

Cold booted (x5) the system and instead of seeing "TPM error
(2314)...selftest" messages, I see the following (expected) messages:

Mar 28 18:35:01 1K5JB02 kernel: ACPI: TPM2 0x76D537C8 34 (v03 Tpm2Tabl 
0001 AMI )
Mar 28 18:35:01 1K5JB02 kernel: tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, 
rev-id 4)
Mar 28 18:35:01 1K5JB02 kernel: tpm tpm0: A TPM error (2314) occurred 
attempting the self test

Verified that the TPM is operational by running tpm2_listpcrs (version
3.1.3 built from source) using the in-kernel resource manager:

admin@1K5JB02:~$ sudo -i
root@1K5JB02:~# export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH
root@1K5JB02:~# export TPM2TOOLS_TCTI_NAME=device 
TPM2TOOLS_DEVICE_FILE=/dev/tpmrm0
root@1K5JB02:~# tpm2_startup --clear
root@1K5JB02:~# tpm2_listpcrs 

Bank/Algorithm: TPM_ALG_SHA1(0x0004)
PCR_00: 51 3f 1d 55 df 26 29 a2 42 ac 0b bf ae 7d 76 54 ef 91 24 d3
.
.
.


** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
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 fails after cold-boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [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) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-25 Thread Tony Espy
@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...

-- 
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 fails after cold-boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [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) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-22 Thread Tony Espy
@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.
https://bugs.launchpad.net/bugs/1762672

Title:
  TPM intermittently fails after cold-boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.

  This bug was originally reported on a Dell XPS 13, but has also
  recently been reported on a Dell Edge Gateway 3000.

  The bug has been confirmed to be fixed in the current development
  release (19.04/Cosmic).

  [Test Case]
  Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:

  "tpm tpm0: A TPM error (2314) occurred continue selftest"

  Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
  should produce errors.

  As this bug is due to a race condition, ideally this test case would
  be run multiple times (20+ cold boots).

  Once the patch is installed the following error message may still be
  present in the syslog, however attempts to use the TPM should work:

  "tpm tpm0: A TPM error (2314) occurred attempting the self test"

  [Regression Potential]
  The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.

  [Original Description]
  After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:

  [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) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-21 Thread Tony Espy
** 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) occurred continue selftest
-  [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
-  [3.423100] tpm tpm0: TPM self test failed
-  [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
+ [Impact]
+ On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold 
boots. The problem seems to be that the TPM gets into a state where the partial 
self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to 
completion), but instead returns TPM_RC_TESTING (meaning some tests are still 
running in the background). A reboot can sometimes restore TPM functionality.
+ 
+ This bug was originally reported on a Dell XPS 13, but has also recently
+ been reported on a Dell Edge Gateway 3000.
+ 
+ The bug has been confirmed to be fixed in the current development
+ release (19.04/Cosmic).
+ 
+ [Test Case]
+ Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop 
or Server and grep for the following error log message:
+ 
+ "tpm tpm0: A TPM error (2314) occurred continue selftest"
+ 
+ Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools
+ should produce errors.
+ 
+ As this bug is due to a race condition, ideally this test case would be
+ run multiple times (20+ cold boots).
+ 
+ Once the patch is installed the following error message may still be
+ present in the syslog, however attempts to use the TPM should work:
+ 
+ "tpm tpm0: A TPM error (2314) occurred attempting the self test"
+ 
+ [Regression Potential]
+ The chance of regression is low, as this patch was written by a well 
respected kernel developer with deep TPM experience. The patch is also being 
cherry-picked from the upstream stable and LTS kernels, and as mentioned, has 
already landed in Disco.
+ 
+ [Original Description]
+ After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently 
fail on cold boot. The following log messages could be observed in syslog:
+ 
+ [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) occurred continue selftest
+  [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
+  [3.423100] tpm tpm0: TPM self test failed
+  [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
  
  Discussion https://lkml.org/lkml/2017/12/6/284
  
  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: linux-image-generic 4.15.0.13.14
- ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
- Uname: Linux 4.15.0-13-generic x86_64
- ApportVersion: 2.20.9-0ubuntu2
- Architecture: amd64
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  baz2268 F pulseaudio
- CurrentDesktop: XFCE
- Date: Tue Apr 10 11:41:57 2018
- EcryptfsInUse: Yes
- HibernationDevice: RESUME=/dev/mapper/cryptswap1
- InstallationDate: Installed on 2018-03-01 (39 days ago)
- InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
- MachineType: Dell Inc. XPS 13 9360
- ProcFB: 0 inteldrmfb
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
- RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-13-generic N/A
-  linux-backports-modules-4.15.0-13-generic  N/A
-  linux-firmware 1.173
- SourcePackage: linux
- UpgradeStatus: No upgrade log present (probably fresh install)
- dmi.bios.date: 01/25/2018
- dmi.bios.vendor: Dell Inc.
- dmi.bios.version: 2.5.1
- dmi.board.name: 02PG84
- dmi.board.vendor: Dell Inc.
- dmi.board.version: A00
- dmi.chassis.type: 9
- dmi.chassis.vendor: Dell Inc.
- dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
- dmi.product.family: XPS
- dmi.product.name: XPS 13 9360
- dmi.sys.vendor: Dell Inc.

-- 
You received this bug notification because you are a member of 

[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot

2019-02-21 Thread Tony Espy
** 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:
  TPM intermittently fails after cold-boot

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
   [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) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2268 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 10 11:41:57 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1762672] Re: TPM on Dell XPS 13 stopped working after upgrade to 18.04

2019-02-20 Thread Tony Espy
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 a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1762672

Title:
  TPM on Dell XPS 13 stopped working after upgrade to 18.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
   [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) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2268 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 10 11:41:57 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1762672] Re: TPM on Dell XPS 13 stopped working after upgrade to 18.04

2019-02-20 Thread Tony Espy
@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 0001 
AMI  )
14:57:44 [2.703384] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
14:57:44 [2.714914] tpm tpm0: A TPM error (2314) occurred attempting the self 
test

I was able to verify that the TPM is operational by running the
following tpm2-tools commands:

$ sudo tpm2_startup -T device --clear
$ tpm2_nvlist
(produces valid output)

Note - in this case, the system is using the in-kernel resource manager,
which it appears doesn't initialize the TPM, hence the need for using
tpm2_startup to initialize the TPM. The version of tpm2-tools used is
2.1.0.

-- 
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 on Dell XPS 13 stopped working after upgrade to 18.04

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress

Bug description:
   [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) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2268 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 10 11:41:57 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection

2016-06-17 Thread Tony Espy
@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 with the latest rc-proposed
image.

I'll retry on krillin later today.

-- 
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 when phone
  initiates connection

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1557298] Re: [Xenial][Bluez5] Low Energy Keyboard is paired incorrectly

2016-03-24 Thread Tony Espy
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 is paired incorrectly

Status in Unity Control Center:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Failed to pair low energy(bluetooth smart, 4.0 or 4.1) devices
  correctly.

  1. bluetooth smart mouse is being listed as "all type" in bluetooth-
  wizard, however it is able to be paired and use, even repair(i'm
  mentioning this because in some circumstance low energy device can be
  only paired once, bug #1515179)

  2. bluetooth smart keyboard is unable to use after bluetooth-wizard
  says "OK". Also the passcode input is also not acting interactively
  like when pairing with bluetooth 3.0 keyboard.

  Above scenario also being verified with bluetoothctl and blueman.

  -
  More details about versions:

  Environment:
  xenial daily (20160307)
  bluez 5.37-0ubuntu5
  gnome-bluetooth 3.18.2-1ubuntu2
  blueman  2.0.3-1ubuntu1
  bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1)

  Tested devices:
  Designer Mouse, bluetooth smart (pairable, work, re-pair work)
  Designer Keyboard, bluetooth smart (paired, not working)
  BT3.0 keyboard, bluetooth classic (pair and work)
  BT3.0 mouse, bluetooth classic (pair and work)

  -
  In control environment with the same hardware system and devices:
  trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel)
  bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5)

  It works with all above devices but can only be pairing through
  bluetoothctl, since the older bluetooth-wizard does not understand
  bluez 5.x. Everything seems works fine, although there are a lot more
  error messages, but since this bug is more about xenial, please let me
  know if we need more information about this, I'm able to reproduce
  this trusty scenario in anytime.

  -
  Additional note:
  A little clarification, since I'm not sure how far the Bluetooth SIG is going 
to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the 
versioning, I decided to just use what ever I saw on the product box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 15 11:40:12 2016
  InstallationDate: Installed on 2016-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0141B2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:71:CC:39:BD:22  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:862538 acl:39687 sco:0 events:2668 errors:0
TX bytes:26235 acl:904 sco:0 commands:1021 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1560094] Re: Starting bluez service is denied

2016-03-21 Thread Tony Espy
@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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1560094

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  New

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1560094] Re: Starting bluez service is denied

2016-03-21 Thread Tony Espy
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: lp:~bluetooth/bluez/snap-core-rolling

** Attachment added: "wrapper script from bluez5 snap"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+attachment/4606861/+files/command-bluez.wrapper

-- 
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/1560094

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  New

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

2016-03-11 Thread Tony Espy
@Selene

Sorry for updating the status without a comment.  I think my intention
was to get this re-tested on a current image and see if it was still
reproducible.

Looks like Simon has commented about kernel changes that may address the
original issue, so re-assigned to him.


** Changed in: bluez (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 reboot

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2016-03-08 Thread Tony Espy
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"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4593246/+files/krillin-270.cap

-- 
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/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2016-03-08 Thread Tony Espy
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2016-03-08 Thread Tony Espy
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 just like on krillin.

** Attachment added: "btmon trace"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4593244/+files/wily-macair.cap

-- 
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/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2016-03-08 Thread Tony Espy
@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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2016-03-07 Thread Tony Espy
** 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.
https://bugs.launchpad.net/bugs/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2016-03-07 Thread Tony Espy
** 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 following text:
  
  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX
  
  The dialog has "Cancel" and "Confirm PIN" buttons.
  
  The keyboard has no display on which a PIN could be displayed.
  
  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.
  
  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.
  
  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.
  
  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found that
  this requires power cycling the keyboard to clear and cause the PIN
  dialog to be displayed again.
+ 
+ [bluetooth]# show
+ Controller B8:64:91:48:2B:1E
+   Name: Aquaris E4.5 Ubuntu Edition
+   Alias: Aquaris E4.5 Ubuntu Edition
+   Class: 0x1c020c
+   Powered: yes
+   Discoverable: no
+   Pairable: yes
+   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
+   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
+   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
+   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
+   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
+   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
+   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
+   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
+   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
+   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
+   Modalias: usb:v1D6Bp0246d0525
+   Discovering: no
+ 
+ [bluetooth]# devices
+ Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
+ Device DE:76:E2:04:9D:6F BB-9D6F
+ Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
+ Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
+ Device 84:38:35:67:0C:3D ubuntu-0
+ Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
+ Device 00:21:3C:A0:14:A6 Jawbone ERA
+ Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7
+ 
+ Device info *before* pairing attempt:
+ 
+ Device 04:69:F8:C2:A0:09
+   Name: tony espy’s Keyboard
+   Alias: tony espy’s Keyboard
+   Class: 0x002540
+   Icon: input-keyboard
+   Paired: no
+   Trusted: no
+   Blocked: no
+   Connected: no
+   LegacyPairing: no
+   Modalias: bluetooth:v004Cp0267d0066
+ 
+ No changes in any of the attributes after *after* the pairing attempt (
+ output of info command is the same ).

** Attachment added: "syslog from krillin w/bluez debug enabled"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591778/+files/syslog

-- 
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/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu 

[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2016-03-07 Thread Tony Espy
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 desktop systems.

-- 
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/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

2016-03-07 Thread Tony Espy
** 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 subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1551858

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

2016-03-03 Thread Tony Espy
** 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 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 reboot

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]

2016-03-01 Thread Tony Espy
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 Bluetooth version.  The latter has a BT symbol
  on the 'del' key.  To put the BT version in pairing mode, power on the
  keyboard, then briefly hold the FN and 'del' key together and release.
  A green LED at the top right of the keyboard should start flashing
  quickly.
  
  Once in pairing mode, the device will become visible on desktop using
  the BT settings UI, however it's *never* shown in the UI on a device
  running the latest Touch ( OTA9.1+ ).  Note, this includes devices
  running a silo version of bluez 5.37, including both arale and krillin.
  On both devices, the keyboard *is* viewable using bluetoothctl.
  
+ It should be noted that LE keyboard support on touch should be a
+ considered a missing feature.
+ 
  Here's the reported attributes of the device from my macair running
  15.10 + bluez 5.37:
  
  Device DF:08:A9:A0:13:93
-   Name: K830
-   Alias: K830
-   Appearance: 0x03c1
-   Icon: input-keyboard
-   Paired: yes
-   Trusted: no
-   Blocked: no
-   Connected: yes
-   LegacyPairing: no
-   UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
-   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
-   UUID: Device Information  (180a--1000-8000-00805f9b34fb)
-   UUID: Battery Service (180f--1000-8000-00805f9b34fb)
-   UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
-   UUID: Vendor specific   (0001--1000-8000-011f246d)
-   Modalias: usb:v046DpB335d0010
+   Name: K830
+   Alias: K830
+   Appearance: 0x03c1
+   Icon: input-keyboard
+   Paired: yes
+   Trusted: no
+   Blocked: no
+   Connected: yes
+   LegacyPairing: no
+   UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
+   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
+   UUID: Device Information  (180a--1000-8000-00805f9b34fb)
+   UUID: Battery Service (180f--1000-8000-00805f9b34fb)
+   UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
+   UUID: Vendor specific   (0001--1000-8000-011f246d)
+   Modalias: usb:v046DpB335d0010
  
  From bluetoothctl on both my laptop and my desktop, I'm able to pair,
  trust and connect the device, and info reflects these changes, however
  the device never actually connects, it's LED remains blinking fast, and
  the keyboard cannot be used.
  
  Note, before pairing, I issued the command 'agent KeyboardOnly' and
  'default-agent'.

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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 Logitech Living Room Keyboard [LE]

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  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 Bluetooth version.  The latter has a BT symbol
  on the 'del' key.  To put the BT version in pairing mode, power on the
  keyboard, then briefly hold the FN and 'del' key together and release.
  A green LED at the top right of the keyboard should start flashing
  quickly.

  Once in pairing mode, the device will become visible on desktop using
  the BT settings UI, however it's *never* shown in the UI on a device
  running the latest Touch ( OTA9.1+ ).  Note, this includes devices
  running a silo version of bluez 5.37, including both arale and
  krillin.  On both devices, the keyboard *is* viewable using
  bluetoothctl.

  It should be noted that LE keyboard support on touch should be a
  considered a missing feature.

  Here's the reported attributes of the device from my macair running
  15.10 + bluez 5.37:

  Device DF:08:A9:A0:13:93
    Name: K830
    Alias: K830
    Appearance: 0x03c1
    Icon: input-keyboard
    Paired: yes
    Trusted: no
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
    UUID: Device Information  (180a--1000-8000-00805f9b34fb)
    UUID: Battery Service (180f--1000-8000-00805f9b34fb)
    UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
    UUID: Vendor specific   (0001--1000-8000-011f246d)
    Modalias: usb:v046DpB335d0010

  From bluetoothctl on both my laptop and my desktop, I'm able to pair,
  trust and connect the 

[Kernel-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]

2016-03-01 Thread Tony Espy
** 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 a Bluetooth version.  The latter has a BT symbol
+ on the 'del' key.  To put the BT version in pairing mode, power on the
+ keyboard, then briefly hold the FN and 'del' key together and release.
+ A green LED at the top right of the keyboard should start flashing
+ quickly.
  
- 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: 20160107
- version device: 20150911
- version custom: 20150929-2-vivid
+ Once in pairing mode, the device will become visible on desktop using
+ the BT settings UI, however it's *never* shown in the UI on a device
+ running the latest Touch ( OTA9.1+ ).  Note, this includes devices
+ running a silo version of bluez 5.37, including both arale and krillin.
+ On both devices, the keyboard *is* viewable using bluetoothctl.
  
- The device is a Logitech Illuminated Living Room keyboard K830 (
- Bluetooth Smart version; !Unifying version ) with an integrated
- trackpad.
+ Here's the reported attributes of the device from my macair running
+ 15.10 + bluez 5.37:
  
- Device DF:08:A9:A0:13:91
-  Name: K830
-  Alias: K830
-  Appearance: 0x03c1
-  Icon: input-keyboard
-  Paired: no
-  Trusted: no
-  Blocked: no
-  Connected: no
-  LegacyPairing: no
-  UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
-  RSSI: -43
+ Device DF:08:A9:A0:13:93
+   Name: K830
+   Alias: K830
+   Appearance: 0x03c1
+   Icon: input-keyboard
+   Paired: yes
+   Trusted: no
+   Blocked: no
+   Connected: yes
+   LegacyPairing: no
+   UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
+   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
+   UUID: Device Information  (180a--1000-8000-00805f9b34fb)
+   UUID: Battery Service (180f--1000-8000-00805f9b34fb)
+   UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
+   UUID: Vendor specific   (0001--1000-8000-011f246d)
+   Modalias: usb:v046DpB335d0010
  
- The device would come and go in the devices list from bluetoothctl
- A manual scan would bring it back
- I then tried to manually pair and it failed with
- Failed to pair: org.freedesktop.DBus.Error.NoReply
+ From bluetoothctl on both my laptop and my desktop, I'm able to pair,
+ trust and connect the device, and info reflects these changes, however
+ the device never actually connects, it's LED remains blinking fast, and
+ the keyboard cannot be used.
  
- On the latop dmesg reports
- [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]
+ Note, before pairing, I issued the command 'agent KeyboardOnly' and
+ 'default-agent'.

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

-- 
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 Logitech Living Room Keyboard [LE]

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  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 Bluetooth version.  The latter has a BT symbol
  on the 'del' key.  To put the BT version in pairing mode, power on the
  keyboard, then briefly hold the FN and 'del' key together and release.
  A green LED at the top right of the keyboard should start flashing
  quickly.

  Once in pairing mode, the device will become visible on desktop using
  the BT settings UI, however it's *never* shown in the UI on a device
  running the latest Touch ( OTA9.1+ ).  Note, this includes devices
  running a silo version of bluez 5.37, including both arale and
  krillin.  On both devices, the keyboard *is* viewable using
  bluetoothctl.

  Here's the reported attributes of the device from my macair running
  15.10 + bluez 5.37:

  Device DF:08:A9:A0:13:93
Name: K830
Alias: K830
Appearance: 0x03c1
Icon: input-keyboard
Paired: yes
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information  (180a--1000-8000-00805f9b34fb)
UUID: Battery Service (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device (1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (0001--1000-8000-011f246d)
 

[Kernel-packages] [Bug 1531925] Re: Can't connect Logitech Living Room Keyboard [LE]

2016-03-01 Thread Tony Espy
** 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 Logitech Living Room Keyboard [LE]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  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: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  The device is a Logitech Illuminated Living Room keyboard K830 (
  Bluetooth Smart version; !Unifying version ) with an integrated
  trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection

2016-03-01 Thread Tony Espy
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 paired
2. Pair the device
3. Make a phone call
4. Try to end the call from the headset

** Summary changed:

- [Jawbone ERA] HFP features not working with Bluez5
+ [Jawbone ERA] HFP features not working with Bluez5 when phone initiates 
connection

-- 
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 when phone
  initiates connection

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2016-02-29 Thread Tony Espy
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 silo 47, which fixes a
regression in rc-proposed on arale and krillin.

-- 
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

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2016-02-29 Thread Tony Espy
** 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 Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2016-01-28 Thread Tony Espy
@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 Ubuntu.
https://bugs.launchpad.net/bugs/1479438

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu RTM:
  Confirmed

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2016-01-28 Thread Tony Espy
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

-- 
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/1479438

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu RTM:
  Confirmed

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2016-01-28 Thread Tony Espy
** 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.
https://bugs.launchpad.net/bugs/1479438

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu RTM:
  Confirmed

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-25 Thread Tony Espy
** 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 in Ubuntu:
  Incomplete

Bug description:
  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: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  
  The device is a Logitech keyboard with an integrated trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-25 Thread Tony Espy
** 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: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid
  
- 
- The device is a Logitech keyboard with an integrated trackpad.
+ The device is a Logitech Illuminated Living Room keyboard K830 (
+ Bluetooth Smart version; !Unifying version ) with an integrated
+ trackpad.
  
  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43
  
  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  
  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

-- 
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 Ubuntu:
  Incomplete

Bug description:
  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: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  The device is a Logitech Illuminated Living Room keyboard K830 (
  Bluetooth Smart version; !Unifying version ) with an integrated
  trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-25 Thread Tony Espy
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
bluetoothctl

 - At some point, 'bluetoothctl info' shows that the device is paired &
connected, however the keyboard BT indicator is still blinking, which
means the keyboard is still in pairing mode, and it cannot be used.

 - When I attempt to connect using gattool, I get the following error:

Attempting to connect to DF:08:A9:A0:13:92
Error: connect error: Transport endpoint is not connected (107)

I also see the following error messages in my syslog:

Jan 25 12:06:24 shrike bluetoothd[949]: Unable to register GATT service with 
handle 0x0046 for device DF:08:A9:A0:13:92
Jan 25 12:06:24 shrike bluetoothd[949]: Report Map read failed: Attribute 
requires authentication before read/write
Jan 25 12:06:24 shrike bluetoothd[949]: Protocol Mode characteristic read 
failed: Attribute requires authentication before read/write
Jan 25 12:06:24 shrike bluetoothd[949]: HID Information read failed: Attribute 
requires authentication before read/write
Jan 25 12:06:25 shrike bluetoothd[949]: Read Report Reference descriptor 
failed: Attribute requires authentication before read/write

 - I was able to use the device with my new iMac, which is running El
Capitan.  When I pair the keyboard, I'm prompted for a PIN code.

So, it looks like PIN authentication isn't being handled properly for
this keyboard.

-- 
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 Ubuntu:
  Incomplete

Bug description:
  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: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  The device is a Logitech Illuminated Living Room keyboard K830 (
  Bluetooth Smart version; !Unifying version ) with an integrated
  trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1531925] Re: bluetoothd crash with BTLE keyboard

2016-01-25 Thread Tony Espy
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 Ubuntu:
  Incomplete

Bug description:
  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: 20160107
  version device: 20150911
  version custom: 20150929-2-vivid

  The device is a Logitech Illuminated Living Room keyboard K830 (
  Bluetooth Smart version; !Unifying version ) with an integrated
  trackpad.

  Device DF:08:A9:A0:13:91
   Name: K830
   Alias: K830
   Appearance: 0x03c1
   Icon: input-keyboard
   Paired: no
   Trusted: no
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
   RSSI: -43

  The device would come and go in the devices list from bluetoothctl
  A manual scan would bring it back
  I then tried to manually pair and it failed with
  Failed to pair: org.freedesktop.DBus.Error.NoReply

  On the latop dmesg reports
  [357895.395029] traps: bluetoothd[790] general protection ip:56419e2c0306 
sp:7ffefd2b6760 error:0 in bluetoothd[56419e217000+105000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531925/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1533716] Re: Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system

2016-01-15 Thread Tony Espy
** 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

** Branch linked: lp:~morphis/ofono/ota9-suspend-fix

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bluez (Ubuntu RTM)
   Status: New => Invalid

** Changed in: ofono (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

** Changed in: ofono (Ubuntu RTM)
 Assignee: (unassigned) => 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/1533716

Title:
  Delay of approx. 60 seconds when an outgoing call is innitiated by the
  IN CAR bluetooth system

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Confirmed
Status in bluez package in Ubuntu RTM:
  Invalid
Status in ofono package in Ubuntu RTM:
  In Progress

Bug description:
  My system:

  current build number: 228
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-13 08:28:26
  version version: 228
  version ubuntu: 20160113
  version device: 20160108-efc96d8
  version custom: 2015--36-46-vivid

  Since several days (not weeks, so something has changed in the last
  couple days!) I have the following situation with my BQ 4.5 in my car.
  When I initiate a call from the IN CAR system (where my phone is
  connected to) I experience sometimes the normal behaviour that the
  call is directly established.

  Sometimes nothing happens. The call is not established and my in car system 
says that the attempt to carry out a call has failed (this message comes after 
approx. 15 seconds after initiation of the call).
  Then approx. 60 seconds after the initiation of the call the call is all of a 
sudden established (without any further interaction). I currently was not able 
to find a logic in this. Here my "log"-file of what I did today:

  -

  13.01.2016

  9:00 h call initiated from car, call directly established
  9:03 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:06 h call initiated from car, call directly established
  9:09 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established

  9:26 h New pairing between phone and car, retry

  9:30 h call initiated from car, call directly established
  9:33 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:36 h call initiated from car, call directly established
  9:39 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:42 h call initiated from car, call directly established
  9:45 h call initiated from car, call directly established (this time again 
via phone book)
  9:48 h call initiated from car (via voice command), approx. 60 sec. delay 
between initiation and call being established
  9:52 h call initiated from phone itself, call established and correctly 
routed via car speaker

  I have added the syslog, upstart-files to the bug report for further
  analysis.

  Uranicus

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533716/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1533716] Re: Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system

2016-01-15 Thread Tony Espy
** 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 (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
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/1533716

Title:
  Delay of approx. 60 seconds when an outgoing call is innitiated by the
  IN CAR bluetooth system

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Fix Committed
Status in bluez package in Ubuntu RTM:
  Invalid
Status in ofono package in Ubuntu RTM:
  Fix Committed

Bug description:
  My system:

  current build number: 228
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-13 08:28:26
  version version: 228
  version ubuntu: 20160113
  version device: 20160108-efc96d8
  version custom: 2015--36-46-vivid

  Since several days (not weeks, so something has changed in the last
  couple days!) I have the following situation with my BQ 4.5 in my car.
  When I initiate a call from the IN CAR system (where my phone is
  connected to) I experience sometimes the normal behaviour that the
  call is directly established.

  Sometimes nothing happens. The call is not established and my in car system 
says that the attempt to carry out a call has failed (this message comes after 
approx. 15 seconds after initiation of the call).
  Then approx. 60 seconds after the initiation of the call the call is all of a 
sudden established (without any further interaction). I currently was not able 
to find a logic in this. Here my "log"-file of what I did today:

  -

  13.01.2016

  9:00 h call initiated from car, call directly established
  9:03 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:06 h call initiated from car, call directly established
  9:09 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established

  9:26 h New pairing between phone and car, retry

  9:30 h call initiated from car, call directly established
  9:33 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:36 h call initiated from car, call directly established
  9:39 h call initiated from car (phone book), approx. 60 sec. delay between 
initiation and call being established
  9:42 h call initiated from car, call directly established
  9:45 h call initiated from car, call directly established (this time again 
via phone book)
  9:48 h call initiated from car (via voice command), approx. 60 sec. delay 
between initiation and call being established
  9:52 h call initiated from phone itself, call established and correctly 
routed via car speaker

  I have added the syslog, upstart-files to the bug report for further
  analysis.

  Uranicus

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533716/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2016-01-15 Thread Tony Espy
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
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

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2016-01-11 Thread Tony Espy
@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 it continually read as full after the car restart?

I recently made some improvement to the way the battery level is
monitored, however these changes have no yet landed in our proposed
images.  I'll discuss with my team and see if we can land this before
the deadline for 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/1479438

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  Fix Committed
Status in bluez package in Ubuntu:
  Fix Released
Status in ofono package in Ubuntu:
  Fix Released
Status in ofono package in Ubuntu RTM:
  Fix Released

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1531515] Re: Bluetooth cannot be enabled on Ubuntu Touch rc-proposed Nexus 4

2016-01-06 Thread Tony Espy
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 that toggling BT off and back on again works as
expected.

A quick look at the syslog shows that the bluez5 version of bluetoothd
was only started at 14:41:46 which appears to be after the final reboot
mentioned in comment #2.  The previous version of bluetoothd running on
the phone was 4.101, which was started at 12:05:44.

@Willem, what time did you flash the device?

My guess is this may have been some kind of system update hiccup.

-- 
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 Nexus 4

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After switching from OTA8.5 to rc-proposed (to test if my BT keyboard would 
work with that) BT cannot be turned on any more.
  I can flip the switch, but after 30s it is switched off again (probably never 
turned on).
  I am unable to discover any BT devices.

  Running bluetoothctl on the devices from the terminal and then entering 
"show" results in:
  "No default controller available"

  I switched to rc-proposed for the Nexus 4 like this:
  ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531515/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1531515] Re: Bluetooth cannot be enabled on Ubuntu Touch rc-proposed Nexus 4

2016-01-06 Thread Tony Espy
** 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 Nexus 4

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After switching from OTA8.5 to rc-proposed (to test if my BT keyboard would 
work with that) BT cannot be turned on any more.
  I can flip the switch, but after 30s it is switched off again (probably never 
turned on).
  I am unable to discover any BT devices.

  Running bluetoothctl on the devices from the terminal and then entering 
"show" results in:
  "No default controller available"

  I switched to rc-proposed for the Nexus 4 like this:
  ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531515/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1080507] Re: Bluetooth printing does not work

2016-01-06 Thread Tony Espy
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, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1080507

Title:
  Bluetooth printing does not work

Status in ubuntu-nexus7:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  I have applied the workaround of bug 1070770, running bluetoothd under
  valgrind to prevent it from crashing. See

  https://wiki.ubuntu.com/Nexus7/UsingTheDevice#Stabilizing_the_Bluetooth_stack

  After successfully connecting my Bluetooth keyboard I tried to connect
  with a Bluetooth printer, the Photosmart Premium C309g-m. To do so,
  the "bluetooth" CUPS backend needs to detect the printer. On a
  standard Intel-based computer I get

  till@till:~$ /usr/lib/cups/backend/bluetooth 
  direct bluetooth://002655096A9C "Photosmart Premium C309g-m" "Photosmart 
Premium C309g-m (Bluetooth)"
  till@till:~$ 

  On the Nexus 7 the same call of the bluetooth backend does not show
  any answer and never exits, probably hanging during the communication
  with the printer.

  Using the bluez-tools on the Nexus 7 I get:

  ubuntu@nexus7-pyongyangs:~$ bt-adapter -d
  Searching...

  [00:26:55:09:6A:9C]
Name: (null)
Alias: 00-26-55-09-6A-9C
Address: 00:26:55:09:6A:9C
Icon: printer
Class: 0x140680
LegacyPairing: 0
Paired: 0
RSSI: -65

  Done
  ubuntu@nexus7-pyongyangs:~$ sudo bt-device -c 00:26:55:09:6A:9C
  [sudo] password for ubuntu: 
  Connecting to: 00:26:55:09:6A:9C
  Agent registered
  Error: Did not receive a reply. Possible causes include: the remote 
application did not send a reply, the message bus security policy blocked the 
reply, the reply timeout expired, or the network connection was broken.
  ubuntu@nexus7-pyongyangs:~$

  The error message of the second command only showed up after waiting
  some seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1080507/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2015-12-22 Thread Tony Espy
** 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

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

2015-12-22 Thread Tony Espy
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 tag: OTA-8.5
version device: 20150911
version custom: 20151210

Can't reproduce on mako 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 tag: OTA-8.5
version device: 20150911
version custom: 20151210

Can't reproduce on arale running OTA-8.5 ( stable/meizu.en #8 ); tested
both with and without a valid SIM card.

-- 
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/1488170

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

  Boot with bluetooth disabled
  Turn on flight mode
  turn off flight mode
  Bluetooth gets enabled

  See bug #1421249 for related symptoms

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2015-12-21 Thread Tony Espy
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 added: "krillin-syslog-20151221"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+attachment/4538456/+files/krillin-syslog-20151221

-- 
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

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2015-12-21 Thread Tony Espy
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 update: 2015-12-21 18:30:51
version version: 24
version ubuntu: 20150713
version device: 20150529-8e13c5f
version custom: 20150713


** Attachment added: "krillin-syslog-20151221-2"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+attachment/4538525/+files/krillin-syslog-20151221-2

** Changed in: bluez (Ubuntu)
   Importance: Undecided => High

-- 
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

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2015-12-18 Thread Tony Espy
@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 with Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2015-12-17 Thread Tony Espy
** 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.
https://bugs.launchpad.net/bugs/1527354

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2015-12-17 Thread Tony Espy
** 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.
https://bugs.launchpad.net/bugs/1527354

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] [NEW] [Jawbone ERA] HFP features not working with Bluez5

2015-12-17 Thread Tony Espy
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 HFP
1.5.

I can pair the device with my krillin, and it properly auto connects (
note, this seems to work better than my iPhone ).   In-call audio works
for both incoming and outgoing calls, however I get no ringtone in the
headset and as mentioned above, I can't answer or terminate the call.
I've verified on my iPhone6, that the headset works.  In addition to a
ringtone in the earpiece, the headset also announces the incoming phone
number.

>From looking at the ofono debug output, I'm never seeing a new HFP
connection occur.  I noticed as the upower plugin uses a foreach_atom
(HFP) style call to update the battery indicators on all attached HFP
devices.

I've tested this extensively on krillin, running rc-proposed:

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 205
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-12-16 17:53:19
version version: 205
version ubuntu: 20151216
version device: 20151204-2254a36
version custom: 2015--36-46-vivid

I've also tested on mako, rc-proposed ( #317 ).

For reference here's the versions of bluez, ofono, and PulseAudio on the
device:

bluez   5.36-0ubuntu2~overlay1
ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
pulseaudio  1:6.0-0ubuntu9.11

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bluez5

** Tags added: bluez5

-- 
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

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2015-12-17 Thread Tony Espy
** 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.
https://bugs.launchpad.net/bugs/1527354

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

2015-12-17 Thread Tony Espy
** 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.
https://bugs.launchpad.net/bugs/1527354

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  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 HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1527354/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

2015-12-16 Thread Tony Espy
@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 to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1418040

Title:
  Calling from car using bluetooth, call is placed on ril_0, even though
  ril_1 is default

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu RTM:
  Triaged

Bug description:
  What happened
  Placed call from car over bluetooth
  Call was placed on my first SIM card, even though I selected my second SIM as 
default for calls

  What should have happened
  The call should have been placed on my second SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150124-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:25:44 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2015-12-03 Thread Tony Espy
@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 20 and add 1, giving us roughly five equal ranges in
20% increments.

If the battery display in the car has only four bars ( as opposed to
five ), then it's not going to match up correctly, and the results will
be skewed.   I'm changing the ofono task to Incomplete.

@Uranicus

Thanks for your thorough testing!  When testing non-standard images (
eg. from rc-proposed ), please attach the details image information from
the command 'system-image-cli -i' ( run on the device ).

It sounds like Bluez5 improves one of the two original devices in your
description ( eg. the Jabra ), however there still are some issues with
it.  I'll leave it up to Simon as to whether he'd like you to open a new
bug for the specific re-connection failure described.

More work is needed apparently to get things working with your A3.

Also, regarding your A3, I'd be interested if it displays more bars for
the phone battery level than the Seat.

** Changed in: ofono (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/1500242

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2015-12-03 Thread Tony Espy
** 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 is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1500242

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  New

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2015-10-22 Thread Tony Espy
** 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) => Tony Espy (awe)

-- 
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/1479438

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  In Progress
Status in ofono package in Ubuntu RTM:
  Fix Committed

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience

2015-10-21 Thread Tony Espy
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.
https://bugs.launchpad.net/bugs/1479438

Title:
  IN CAR: Battery levels not shared via bluetooth for in car experience

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 
2013 in my instance)

  1. Connect the DUT to the car
  2. On the display panel the battery always shows full

  EXPECTED:
  I expect to see the actual level of the battery on the device

  ACTUAL:
  The display always shows the battery at 100% I assume the default if no info 
is available.

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp