[Bug 1510570] Re: Bluetooth LE pairing fail

2020-08-29 Thread su san
If you are using mobile Bluetooth the pairing with other device will fail if 
your software  is not so updated. the floating Bluetooth software can be repair 
 by   [URL=https://www.uaetechnician.com/mobile-repair-services.html/]mobile 
repair dubai [/URL] 
so that  you can  continue with mobile  Bluetooth pairing with any other 
devices.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2020-04-24 Thread Rex Tsai
** Changed in: oem-priority
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-06-29 Thread Łukasz Zemczak
Bug-fix not verified for 161 days - removing the update from -proposed
as per SRU policy.

** Changed in: bluez (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-05-22 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-03-26 Thread Daniel van Vugt
I'm not sure. I'm only going on Cyrus' comments.

Maybe check with koza for some extra verification on this one.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-03-26 Thread Łukasz Zemczak
Should this bug be switched to verification-failed-xenial in that case?
What is the status of this SRU?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-03-19 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Importance: Critical => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-02-12 Thread Daniel van Vugt
Being a HWE problem, and not completely patchable, it sounds like we may
have to consider a major upgrade of bluez to xenial. Assuming we can
avoid ABI/API breaks...

I don't think we want to do it, but if it comes to that then we may have
to.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-02-12 Thread Cyrus Lien
With bluez 5.37-0ubuntu5.2 Designer keyboard still can not connect on
4.13.0-32-generic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-02-12 Thread Cyrus Lien
Designer keyboard still can not connect on 4.13.0-32-generic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-02-09 Thread Cyrus Lien
Verified bluez 5.37-0ubuntu5.2 from -proposed, designer mouse works but
designer keyboard failed.

To fully support BT LE, looks like we need to upgrade bluez >5.44.
(verified bluez 5.46-0ubuntu4~somerville1 which comes form artful can
make designer keyboard works)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-02-08 Thread Łukasz Zemczak
Since the regression has been resolved, could someone re-validate the
package in -proposed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-01-28 Thread Daniel van Vugt
Good news: Bug 1744806 has been resolved with a kernel update. So we're
still able to continue testing and releasing this one.

** Tags removed: verification-failed verification-failed-xenial
** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-01-23 Thread cement_head
Verification failed on Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-01-22 Thread Daniel van Vugt
Verification failed on xenial. Please see bug 1744806.

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-01-18 Thread Łukasz Zemczak
Hello Guilhem, or anyone else affected,

Accepted bluez into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.37-0ubuntu5.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: bluez (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-01-10 Thread Konrad Zapałowicz
** Description changed:

  [Impact]
  
  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.
  
  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.
  
  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.
  
  [Original Report]
  
  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.
  
  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
  
  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.
  
  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  
  [Test Case]
  
- Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
- Remove file 50-bluetooth-hci-auto-poweron.rules located in
- /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
- powered off now.
+ On xenial install from ppa:
+ https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
+ 
+ Now reboot the machine. The BT adapter shall be
+ powered on.
  
  [Regression Potential]
  
- Cannot think of any
+ If things go wrong the adapter will not be powered on after the system
+ boots up. Therefore while testing please focus on the adapter state,
+ i.e. powered on or off.
  
  [Other Info]
  
  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

** Description changed:

  [Impact]
  
  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.
  
  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.
  
  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.
  
  [Original Report]
  
  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.
  
  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
  
  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.
  
  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  
  [Test Case]
  
  On xenial install from ppa:
  https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
  
  Now reboot the machine. The BT adapter shall be
  powered on.
  
  [Regression Potential]
  
  If things go wrong the adapter will not be powered on after the system
  boots up. Therefore while testing please focus on the adapter state,
  i.e. powered on or off.
  
  [Other Info]
  
  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22
+ 
+ [What to upload]
+ 
+ For xenial as in:
+ 
+ ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
+ ) 
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2018-01-01 Thread Yuan-Chen Cheng
** Tags removed: risk

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2017-12-19 Thread Yuan-Chen Cheng
** Tags added: sru

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2017-12-18 Thread Yuan-Chen Cheng
** Tags added: risk

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2017-12-18 Thread Konrad Zapałowicz
Testing::

1. using the bluez without the patch

- reboot
- try to pair and connect

2. using bluez with patch

- reboot
- try to pair and connect

In some cases pairing and connecting works better with the patch
applied. There is no negative behavior observed with patch applied
compared to w/o the patch.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2017-12-18 Thread Yuan-Chen Cheng
** Changed in: oem-priority
 Assignee: (unassigned) => Cyrus Lien (cyruslien)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2017-12-18 Thread Konrad Zapałowicz
** Changed in: bluez (Ubuntu Xenial)
 Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2017-12-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2017-11-08 Thread Yuan-Chen Cheng
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510570] Re: Bluetooth LE pairing fail

2017-05-04 Thread Robie Basak
Adding a task for Xenial as requested on IRC. But note that I haven't
looked into the details of the proposed fix - in particular checking for
and understanding any proposed change in behaviour for Xenial users. So
please don't take this as a +1 from ~ubuntu-sru. Before accepting this
SRU, please consider whether the proposed fix is appropriate from
scratch.

** Also affects: bluez (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1510570] Re: Bluetooth LE pairing fail

2017-05-04 Thread Konrad Zapałowicz
** Description changed:

- On 15.10 we now have bluez 5 so we can pair BLE devices like the
+ [Impact]
+ 
+ When the Bluetooth adapter is not powered on it is not possible to use
+ it in normal way. We used to have a hack to force powering on by using
+ an udev rule but this doe snot work anymore. Luckily the BlueZ has
+ introduced "AutoEnable" option that makes the stack power on adapters by
+ itself.
+ 
+ Backporting this to xenial will improve life of the desktop users and
+ will not require them to hack the solution on their own. The fix itself
+ uses the well known solution to this problem that is floating around
+ there for a while.
+ 
+ The upload fixes the bug by enabling the 'AutoEnable' option in the
+ bluetoothd config file.
+ 
+ [Original Report]
+ 
+ . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.
  
  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
  
  This is due to udev rule that use "hcitool" to power on device.
- Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.
+ Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
+ instead of udev rules.
  
- here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
- And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable
+ here is a commit with this parameter:
+ http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
+ 
+ [Test Case]
+ 
+ Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
+ Remove file 50-bluetooth-hci-auto-poweron.rules located in
+ /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
+ powered off now.
+ 
+ [Regression Potential]
+ 
+ Cannot think of any
+ 
+ [Other Info]

** Description changed:

  [Impact]
  
  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.
  
  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.
  
  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.
  
  [Original Report]
  
  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.
  
  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
  
  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.
  
  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  
  [Test Case]
  
  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.
  
  [Regression Potential]
  
  Cannot think of any
  
  [Other Info]
+ 
+ This fix is included in the development release, see:
+ http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1510570] Re: Bluetooth LE pairing fail

2017-05-04 Thread Daniel van Vugt
See also:
http://www.bluez.org/release-of-bluez-5-44/

** Summary changed:

- BLE pairing fail
+ Bluetooth LE pairing fail

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs