The change is intended - please check comment #3.
--
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/1510570
Title:
BLE pairing fail
Status in bluez package in Ubuntu:
Incomplete
Bug
Rejecting from the Xenial queue due to the lack of response.
If this still needs fixing in Xenial, please see
https://wiki.ubuntu.com/StableReleaseUpdates and follow
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.
--
You received this bug notification because you are a member of Kernel
Additionally, were these changes intended? They are not documented in
the changelog.
1 diff -Nru bluez-5.37/debian/50-bluetooth-hci-auto-poweron.rules
bluez-5.37/debian/50-bluetooth-hci-auto-poweron.rules
2 --- bluez-5.37/debian/50-bluetooth-hci-auto-poweron.rules 2016-03-01
I see this was uploaded to Xenial as well as an SRU. It would be helpful to
fill out the template in order to make reviewing easier:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
In addition we must ensure it is fixed in the development release before it
gets fixed in stable
I don't know guys. None of the above helped me. I initially had Killer
1535 card on my DELL XPS 13. Today I replaced it with Intel 8260 ant it
still doesn't see Mobile Bluetooth 3600 mouse. Oddly it worked on
another laptop with Intel 7260 card. Go figure :(
--
You received this bug notification
Apologize, not 26, but 27. Haven't found how to edit my previous
comment.
--
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/1510570
Title:
BLE pairing fail
Status in bluez package in
#23 resolved my problem, I haven't changed any other files, like 25 and
26 suggested.
--
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/1510570
Title:
BLE pairing fail
Status in bluez
@All
FYI: the fix discussed here is on it's way to zesty [currently being
tested]. Moreover we are making efforts on getting it as an update to
xenial.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Thanks to you,
Got both Designer keyboard and Mouse working on Ubuntu 16.04
comment #34 solves the issue.
notice: without upgrading to v5.40 only the designer mouse will work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
** Tags added: xenial
** Tags added: yakkety
--
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/1510570
Title:
BLE pairing fail
Status in bluez package in Ubuntu:
Confirmed
Bug
Finally both keyboard and mouse Microsoft Designer are working
perfectly!
- I used #25 (maybe #27 can work, I didn't try)
- then #23 worked perfectly using this script:
https://gist.github.com/Powiee/06129701f78f3c8a9cd23c197a35130f
- I removed all BT devices using bluetoothctl (command line
** Tags added: papercuts2017
--
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/1510570
Title:
BLE pairing fail
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15.10
I made the same as #25 and I got the following:
1) the following dmesg error desappeared. The BT controller is an internal usb
device.
[ 17.566030] usb 2-6: device descriptor read/64, error -110
2) M$ Bluetooth Mobile Mouse 3600 works. I removed any traces of it with
bluetoothctl and I started
Based on comments here I can get the Microsoft Arc Touch Bluetooth to
pair. But the Bluetooth manager doesn't think it is a mouse, or offer
connecting it to the input service. How does one get an actual working
mouse?
--
You received this bug notification because you are a member of Kernel
Thanks for this. I managed to get my Arc Touch SE mouse to work with an
otherwise stock 16.04 system by changing the setting as mentioned in
#25, COMMENTING OUT the rule in #27 (merely changing it didn't seem to
work) and then connecting as in #16.
Very grateful, as the mouse was a Christmas
Hi Guys, thank you all for the effort, I can confirm that post #25 & #27
works as expected! (including the step of removing/renaming file 50
-bluetooth-hci-auto-poweron.rules)
Many thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Just confirmed that Gyula's notes work for me too. Post #'s 25 & 27 work
great to get my Microsoft Arc BTLE Mouse paired. Flawless connect,
disconnect, and general usage. Thanks guys!
What I did:
- editing /etc/bluetooth/main.conf as it is said in #25
- editing
Hi guys. I am happy about finding this page. I had the same issue with
my new Dell Bluetooth Mouse WM615 but after using your suggestions, it's
working well now.
What I did are
- editing /etc/bluetooth/main.conf as it is said in #25
- editing /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules
I tried to specify the udev rule more precisely, i.e. only power up a host
controller.
Is there anybody could give it a try?
#/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules
# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*",
ENV{DEVTYPE}=="host",
After removed the udev rule, I can pair & connect both Designer Keyboard
and Mouse via bluetoothctl. Both of them works.
Bluez version: 5.37-0ubuntu5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
On 16.10, if i do :
modified the main.conf
sudo gvim /etc/bluetooth/main.conf
change line 67 from #[Policy] into [Policy]
change line 89 from #AutoEnable=false into AutoEnable=true
remove file 50-bluetooth-hci-auto-poweron.rules located in
/lib/udev/rules.d
My mouse
I'm on ubuntu 16.10 and not works for me for both Designer keyboard and
mouse. Do you have any solution before an official 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/1510570
Bluez 5.40 works for me for both Designer keyboard and mouse. At this
time Ubuntu has not packaged it up into a DEB but I was able to build
and install it myself (search for bluez 5.40 to find how to download the
entire large source). I am using Ubuntu 16.04 but a newer kernel made by
Ubuntu
I try another merge request with AutoEnable parameter here:
https://code.launchpad.net/~guilhem-fr/bluez/ubuntu-autoenable/+merge/296115
It's based on previous patch submit here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
i confirm that Micosoft Designer mouse cannot work in ubuntu 16.04 at NUC5i7RYH
i7-5557U.
The BT panel sais that the device is connected. Yet, mouse does not move the
cursor
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
I confirm that Microsoft Arch Tech mouse cannot be paired with Asus Eee
PC. I'm using Ubuntu 16.04 Linux earth 4.4.0-22-generic #40-Ubuntu SMP
Thu May 12 22:03:15 UTC 2016 i686 i686 i686 GNU/Linux. Bluez version
5.37-0ubuntu5
--
You received this bug notification because you are a member of
I've confirmed this issue on multiple dell platforms including xps 9343,
9350, & 5510 laptops, both broadcom & intel wireless radios, & multiple
types of LE devices.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
I've got the problem on Ubuntu 16.04 LTS Desktop :(
--
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/1510570
Title:
BLE pairing fail
Status in bluez package in Ubuntu:
Confirmed
Bug
Hi Nahum Rozen (nahum),
in Ubuntu 16.04Lts Desktop Edition that ppa doesn't work, it gves this
error:
W: The repository 'http://ppa.launchpad.net/guilhem-fr/bluez-autoenable/ubuntu
xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is
found a workaround to this:
if you happened to upgrade from vivid(15.04) or you know how to get vivid
kernel install properly,
you can boot the system with 3.19 kernel and pairing up the mouse using
bluetoothctl manually
then reboot with 4.2, the mouse will still paired and working.
$
** Bug watch added: Email to 1398738509@qq #
mailto:1398738...@qq.com
** Also affects: bluez via
mailto:1398738...@qq.com
Importance: Undecided
Status: New
** No longer affects: bluez
--
You received this bug notification because you are a member of Kernel
Packages, which is
The 4.4 Linux Kernel series reconnects even after the 10 minutes or
(usually) a reboot. My roll-your-own is 4.4-rc2 which has a building
problem but that is known and probably will already be fixed in rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is
A follow-up. My Android Lollipop phone can connect and knows that the
Designer Mouse is a mouse (not an unknown). Unfortunately it too loses
connection in 10 minutes so the problem is deeper than I had expected.
--
You received this bug notification because you are a member of Kernel
Packages,
I have been working with a Microsoft Designer Mouse (also a BLA device).
I went to AskUbuntu to try to find out why I could not use it with
Ubuntu 15.10. [I have a Microsoft Surface Pro3 and am using a home-built
kernel but the kernel does not seem to affect this problem.] I have
followed the
Cancel that.
Rebooted one more time, and of course it works perfectly minutes after
calling for help.
Cheers!
--
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/1510570
Title:
BLE pairing
I have followed Nahum's overview of steps and not had much success.
It does at least claim to be paired now, but not actually doing
anything. Tried pairing from scratch several times, sometimes it pairs
and sometimes doesn't.
In my case there was no 50-bluetooth-hci-auto-poweron.rules file to
@nahum, no you did it right.
You may have to remove mouse and redo pairing from scratch.
If it doesn't work, try to move udev rule to another backup dir.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
@nahum have you try my ppa or you only have modify your main.conf?
you also have to remove udev rules
--
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/1510570
Title:
BLE pairing fail
Hi Guilhem,
I only did the modify my main.conf.
Can you send detailed instructions regarding what to do?
Thanx
--
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/1510570
Title:
BLE
Hi Guilhem,
Did what you said:
Add your PPA:
sudo add-apt-repository ppa:guilhem-fr/bluez-autoenable
sudo apt-get update
sudo apt-get upgrade
modified the main.conf
sudo gvim /etc/bluetooth/main.conf
change line 67 from#[Policy]into [Policy]
** 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/1510570
Title:
BLE pairing fail
Status in bluez package in Ubuntu:
Ah, thanks Simon. As you currently seem to manage bluez
(https://code.launchpad.net/~bluetooth/bluez/bluez5-upgrade), can you do
this change too?
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of
Hi,
I encountered the very same issue. Followed changing AutoEnable=true, did't
helped...
I'm with 15.10 without any mods.
Any ideas?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
@Mathieu: Is enabling "AutoEnable" something we want to do and is
generally safe?
--
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/1510570
Title:
BLE pairing fail
Status in bluez package
@pitti: Yes, they implemented it to allow us to replace our hack udev
rule
(https://bazaar.launchpad.net/~bluetooth/bluez/ubuntu/view/head:/debian/50
-bluetooth-hci-auto-poweron.rules) with that. "that some distributions "
includes Ubuntu.
--
You received this bug notification because you are a
@Martin, changelog from 5.35 is quite explicit:
"
A noteworthy new feature is the ability to configure bluetoothd to
automatically enable (power on) all new adapters. One use of this is to replace
unreliable “hciconfig hci0 up” commands that some distributions use in their
init/udev scripts.
** Description changed:
On 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 informations: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
+ More
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => 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/1510570
48 matches
Mail list logo
