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
** 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
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.
** 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:
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
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
** 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:
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
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
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:
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
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
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
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:
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
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
** 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
** 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:
** 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:
** 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:
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
** 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
** 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
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
** 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
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
** 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.
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
28 matches
Mail list logo
