Hide Forgot
Description of problem: Bluetooth setup - Add new device ignores PIN Options... setting Version-Release number of selected component (if applicable): (FC 16 with most recent updates, but has been there in FC15 and earlier) How reproducible: Always, or at least 95% or more of the time. Rarely it will work properly. Steps to Reproduce: 1. Get a device like a GPS with a fixed pin, e.g. 0000 or 1234 2. Do "add new device" 3. Select PIN options and set correct pin for device Actual results: It does an automatic 6 digit pin which it tells me to type in to the device - which has no way of doing so even though I've gone back and verified that it was actually set in the dialog box before hitting Next. Expected results: It would use the PIN I asked it to use. Additional info:
I'm seeing something similar. Though I set a PIN, I'm always presented with automatic 6 digit PIN I'm suppose to verify on both devices. Not sure if it's relevant, but since F16 I'm not able to connect reliably to my phone. The attemp fails 9/10 times. bluez-4.96-3.fc16.x86_64
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.