The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: bluez (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: blueman (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Tags added: xenial
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired periodically
Status in GNOME Bluetooth:
Fix Released
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=923349.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
How the status of this problem on a clean system with Ubuntu 16.04 or
16.10 or even 17.04?
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to
I can confirm that what I said before isn't valid anymore. What appeared
to be fixed in 15.10 has resurfaced in 16.04, and now I can't fix it
even by myself.
Oh well... I just gave up on suspending.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: blueman (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: blueman (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Also still affects me on Ubuntu 16.04.
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired periodically
Status in GNOME Bluetooth:
** Changed in: blueman (Ubuntu Quantal)
Status: New => Invalid
** Changed in: blueman (Ubuntu Raring)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Also affects: blueman (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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired
... at least on Ubuntu Mate 16.04 which uses blueman
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired periodically
Status in
This is still occurring for me in 16.04 Xenial for me. I've tried both
Ubuntu and Ubuntu Mate. Works in Arch Linux on same machine.
--
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/1094744
Mark,
I fixed this bug in may 2015:
https://bugzilla.gnome.org/show_bug.cgi?id=749443
Version 3.16 (used in Ubuntu 15.10 (Wily) didn't come with the patch and
no one backported.
Version 3.18 (used in Ubuntu 16.04 (Xenial) come with the patch.
Best regards and sorry for any trouble.
** Bug
Can we please get the extra devices into the pin code database.
is still missing in 15.10 (Wily). It is tedious to fix this every 6
months or so.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
You're welcome. I'm very glad the situation improved.
As you can see, I didn't try to filter by type=mouse or name tags, and
was quite generic. It was my first idea, but I'm inclined to believe it
wouldn't matter anyway as the more precise filter would still capture
the device just as well.
Best
Hi Marcos,
I did a clean install of 15.10 yesterday, so I also used that
opportunity to test this issue. In short, pairing using the user
interface still did not work, but adding the OUI to the XML file was
enough to persist the connection across reboots and suspends. No need to
use the command
Thanks David.
I will check this and create and submit a patch.
Cheers.
2015-10-23 15:49 GMT-02:00 David Cesarino de Sousa <1094...@bugs.launchpad.net>:
> Hi Marcos,
>
> I did a clean install of 15.10 yesterday, so I also used that
> opportunity to test this issue. In short, pairing using the
Hi David,
In the version 3.18 of gnome-bluetooth this OUI is already added. May
be someone could backport the patch?
2015-10-23 16:04 GMT-02:00 Marcos Alano :
> Thanks David.
>
> I will check this and create and submit a patch.
>
> Cheers.
>
> 2015-10-23 15:49 GMT-02:00
Did you try add the OUI for your mouse in
/usr/share/gnome-bluetooth/pin-code-database.xml? I thinks there is
many differents OUIs for this model.
PS.: Post your OUI here so I can create and send a patch.
2015-09-05 18:19 GMT-03:00 Rael :
> On 14.04 LTS, bought one of this,
On 14.04 LTS, bought one of this, and I'm facing this issue.
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired periodically
I stand by what I said before. After that comment, I did only these four
steps:
1. Install Ubuntu on a clean partition.
2. Pair and connect using the Bluetooth UI in the Ubuntu desktop (BT icon →
Bluetooth Settings). In other words, use normally.
3. Immediately (not sure if it makes any
Sorry for this problem. The address 30:59:B7: seems correct. Can you
check the batteries? That is a long shot, but may be can be the
problem.
2015-05-17 19:12 GMT-03:00 David Cesarino de Sousa 1094...@bugs.launchpad.net:
Marcos, thanks for your help.
That output was to show that the mouse
Ok. Please do more tests in a clean installation and let us know about
the results.
Cheers.
2015-05-17 19:47 GMT-03:00 Marcos Alano marcoshal...@gmail.com:
Sorry for this problem. The address 30:59:B7: seems correct. Can you
check the batteries? That is a long shot, but may be can be the
Marcos, thanks for your help.
That output was to show that the mouse unpairs after a suspend/reboot.
If I follow the two steps I said before, I get the correct, expected
status (paired), and I can move my mouse. See relevant output now that
it is connected:
[ /org/bluez/663/hci0 ]
After rebooting and still having the problem no matter which line
combination (device or adapter oui, with or without name) in the xml
file I used, I rebooted and tried this command I saw in the
BluetoothSetup community help wiki page:
sudo bluez-test-device trusted 30:59:B7:73:B6:C6 yes
Now it
I have the Sculpt Comfort Bluetooth mouse as well (model H3S-3), and
the connection is not surviving suspends or reboots on Vivid (15.04). To
fix, I need to:
1. Put the mouse into pairing mode (holding the bottom button).
2. Go to the Bluetooth setting for the mouse and activate the
David,
Please connect and pair the mouse. After that execute
bluez-list-devices. If you check the lines:
Connected = 0
Paired = 0
You'll see the mouse is not even connected. The address is the same as
computer Bluetooth adapter so probably because that the line you put
in the file is wrong.
This problem has reappeared in 15.04 (Vivid Vervet). Symptoms exactly as
before.
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to be
Mark, can you find the address of your Sculpt mouse using the command
bluez-list-devices? If the address prefix is different I need submit a
new patch (but I can post a workaround as well).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thanks Mark, help me so much. :)
The problem is in the Bluetooth device address: The prefix (which
indicates the manufacturer) is different for your mouse. So the
workaround is add this line in the file
/usr/share/gnome-bluetooth/pin-code-database.xml (close to the Wedge
mouse entrance):
device
Does this help? Note it is the same mouse that originally gave problems
when this bug first appeared. It is also appearing twice in the list of
devices (there is only one).
Thanks,
Mark
mthornton@mark-PBL21:~$ bluez-list-devices
[ /org/bluez/863/hci0 ]
Address = 00:02:72:C6:AE:86
Powered
I submitted a patch for gnome-bluetooth to add the address of your
device in the PIN DB.
2015-05-15 13:19 GMT-03:00 Mark Thornton 1094...@bugs.launchpad.net:
Working (for now). Pairing now survived a reboot.
Thanks,
Mark
On Friday, 15 May 2015, Marcos Alano 1094...@bugs.launchpad.net wrote:
Working (for now). Pairing now survived a reboot.
Thanks,
Mark
On Friday, 15 May 2015, Marcos Alano 1094...@bugs.launchpad.net wrote:
Thanks Mark, help me so much. :)
The problem is in the Bluetooth device address: The prefix (which
indicates the manufacturer) is different for your mouse.
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: bluez (Ubuntu Quantal)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: gnome-bluetooth (Ubuntu Raring)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Kernel
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: bluez (Ubuntu Raring)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug was fixed in the package gnome-bluetooth - 3.2.2-0ubuntu5.1
---
gnome-bluetooth (3.2.2-0ubuntu5.1) precise-proposed; urgency=low
* debian/patches/99_add_microsoft_mice.patch: add Microsoft Sculpt/Wedge
mouse (LP: #1094744, LP: #1158462). Thanks, Marcos Barbosa, Anton
This bug was fixed in the package gnome-bluetooth - 3.6.0-0ubuntu1.1
---
gnome-bluetooth (3.6.0-0ubuntu1.1) quantal-proposed; urgency=low
* debian/patches/99_add_microsoft_mice.patch: add Microsoft Sculpt/Wedge
mouse (LP: #1094744, LP: #1158462). Thanks, Marcos Barbosa, Anton
I had the same problem with a MS scult confort mouse on an up to date
saucy (with gnome-bluetooth=3.8.1-2ubuntu2)
Proposed fix:
/usr/share/gnome-bluetooth/pin-code-database.xml:
device oui=xx:xx:xx: type=mouse pin=/
followed by a reboot didnt helped
But installing blueman as suggested
** Branch linked: lp:ubuntu/raring-proposed/gnome-bluetooth
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired periodically
it seems that the Sculpt Touch Mouse can only be pair to one computer see here
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/pairing-sculpt-comfort-mouse-to-multiple-computers/8da3698c-d593-4ae7-92b8-4c48fd4ec3d0
just to be aware for your testing.
I have issue with DUAL
Adding device oui=7C:1E:52: type=mouse pin=/
to /usr/share/gnome-bluetooth/pin-code-database.xml
fixed the problem for me with the Microsoft Sculpt Touch Mouse on Ubuntu
12.04 LTS 32Bit.
Thanks for the help.
--
You received this bug notification because you are a member of Kernel
I seem to have a similar problem, on saucy.
Should the fix for this problem be included in standard saucy, or do I
have to do something special to get it?
If the former, I might have a different, new problem.
--
You received this bug notification because you are a member of Kernel
Packages,
Henning, the fix is already in Saucy. You may have a different problem.
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu Raring)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
I have a Microsoft Sculpt Comfort Mouse which was having the same
problem on Kubuntu 13.10 and Ubuntu Gnome 13.10. The problem doesn't
arise on other distros like Fedora 20 (Alpha). Adding the line
device oui=28:18:78: type=mouse name=Microsoft Sculpt Comfort
Mouse pin=/
to
** Changed in: gnome-bluetooth
Status: Incomplete = Fix 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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired
gnome-bluetooth/3.6.1-0ubuntu3.1 in raring-proposed fixed the issue.
** Tags added: verification-done-raring
--
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/1094744
Title:
MS Sculpt
gnome-bluetooth/3.6.0-0ubuntu1.1 in quantal-proposed fixed the issue.
** Tags added: verification-done-quantal
--
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/1094744
Title:
MS Sculpt
gnome-bluetooth/3.2.2-0ubuntu5.1 in precise-proposed also fixed the
issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Hello Jordy, or anyone else affected,
Accepted gnome-bluetooth into raring-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/gnome-
bluetooth/3.6.1-0ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Branch linked: lp:ubuntu/precise-proposed/gnome-bluetooth
** Branch linked: lp:ubuntu/quantal-proposed/gnome-bluetooth
--
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/1094744
Title:
** Branch linked: lp:ubuntu/saucy-proposed/gnome-bluetooth
--
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/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired periodically
Status
56 matches
Mail list logo