If you read the date on the ticket, it was reported against the current
version of Ubuntu at the time. Sure, "Many things change." That
doesn't mean the bug was invalid, it just means you "won't fix."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
I've noticed that the pairing assistant wizard remembers the PIN option
specified when run as root.
I read on the GNOME blog that GNOME 3.10 will have completely re-done Bluetooth
wizard, so this issue (which I'm also experiencing) may be resolved then. I've
installed `blueman` in the interim
The pairing assistant in Ubuntu 12.04.2 LTS is still broken.
Only magical pairing invented by @nh2 works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/618838
Title:
Apple Magic Trackpad requires
Indeed the pairing assistant is broken. It is always trying to use an
automatic 6 digit pin. nh2, the method you have proposed does not work
for me.
Using:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.2 LTS
Release:12.04
Codename: precise
--
The bluetooth pairing assistant is just terribly broken. It simply
doesn't care if you select '' or whatever, it will always try its
6-digit pin.
This is what works for me with paring with my Magic Trackpad:
1) Try to pair with the pin option. It will fail with the 6-digit
number.
I'm also experiencing this, bluez and hidd both fail to connect
(pairing failed / connection refused) but blueman-manager sets up
the pairing perfectly on first try. Dunno why bluez can't handle it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't work for Canonical anymore nor do I have access to this hardware
or interest in it anymore.
It seems the wikipage mentioned in the original bug report above has
been updated quite a bit until June last year, and the original report
was for Ubuntu 10.10.
I'd suggest makeing sure you are
I did not find that Maverick prompted me with an Always grant access
checkbox as shown in the referenced wiki article, so the pairing was
still lost between reboots.
I was forced to use the instructions in
http://ubuntuforums.org/showthread.php?t=1612843, which specify adding
the (unique) device
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/618838
Title:
Apple
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/618838/+attachment/1493963/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/618838/+attachment/1493964/+files/CurrentDmesg.txt
** Attachment added: Lspci.txt
11 matches
Mail list logo
