** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Importance: Undecided => Medium
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Triaged => Invalid
** Tags added: after-bluez5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1390532
Title:
[Bluetooth] Attempt to pair using default pin of 0000 before prompting
the user
Status in bluez package in Ubuntu:
In Progress
Status in ubuntu-system-settings package in Ubuntu:
Invalid
Bug description:
Per the design at https://wiki.ubuntu.com/Bluetooth#phone
If the device is of a type that usually has the PIN “0000” (a headset,
keyboard, or mouse), Ubuntu should try this first. If that doesn’t
work, or for any other kind of device, a ‘PIN for “{headset name}”’ or
‘Passkey for “{headset name}”’ dialog should appear, with a
PIN/passkey field that uses a number-based keyboard.
It is not clear whether the input field should still display 0000
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1390532/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
