I think a workaround (and a path to a patch) is add a line such
device oui=00:00:00 name=Microsoft Wedge Touch mouse type=mouse
pin=/
In the file /usr/share/gnome-bluetooth/pin-code-database.xml (is part of
gnome-bluetooth package).
Just need detect correct OUI value. I think is half value
for PIN for
all mouses and some exception for Apple mouses with PIN codes. Everything
works fine after that - mouse paired with bluetooth applet after adding
automatically and everything works.
Bugfix by Marcos Henrique Esteves Barbosa (marcosestevesbarbosa-gmail)
Patch and tests by Anton
is set to NULL. The bugfix is add a line in the file
+ /usr/share/gnome-bluetooth/pin-code-database.xml for set correct PIN.
Bugfix by Marcos Henrique Esteves Barbosa (marcosestevesbarbosa-gmail)
Patch and tests by Anton Anikin (anton-anikin)
--
You received this bug notification because
Public bug reported:
Actually the test screen for mouse functions (the screen with a little
girl) just show if vertical scroll is working. Today many touchpads and
some mouses come with support to horizontal screen. Is a excellent idea
support configuration and test for this feature.
**
Anton,
Any news? Kernel 3.10 is afected too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158462
Title:
Microsoft Wedge Touch Mouse losing connection
To manage notifications about this bug go
What version of the kernel 3.8 comes with patch to fix this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169984
Title:
3.8.0-18 HDMI/DisplayPort audio regression: Either oops or opening
The problem is relatad with port number. Eg.:
ping linux.dropbox.com:http (not work)
ping linux.dropbox.com (works fine)
The difference is :http part, used to indicate port number.
IMHO is a problem with resolve address code. Its resolving address:port,
but the correct is only resolve address.
