Bluetooth PIN always random

Reported by co0lingFir3 on 2010-05-25
This bug affects 5 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
gnome-bluetooth (Ubuntu)

Bug Description

Binary package hint: bluez


when I want to connect my SE W800i mobile phone to my Asus Eee PC 1005 HA netbook i go to the bluetooth-manager gui and add it. Selecting a different than "Automatic PIN" (e.g. 0000) has no effect however. There is always a random PIN generated.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bluetooth 4.60-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Tue May 25 21:20:54 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: ASUSTeK Computer INC. 1005HA
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=7ab1ecbd-0b96-4920-99b1-8426f94a20df ro quiet splash
SourcePackage: bluez
dmi.bios.date: 02/26/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd02/26/2010:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
 hci0: Type: USB
  BD Address: 00:22:43:FD:5C:E3 ACL MTU: 1021:8 SCO MTU: 64:1
  RX bytes:1007 acl:0 sco:0 events:33 errors:0
  TX bytes:1103 acl:0 sco:0 commands:33 errors:0

co0lingFir3 (coolingfire) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
nh2 (nh2) wrote :

Using Ubuntu 12.04.

This is hilarious. You connect a device that doesn't even have keys (e.g. a wireless touchpad), bluetooth-wizard tells you that it it is a "Tablet" but if you use "automatic pin", it still tells you to enter a six-digit number into the *touchpad*. It should know better.

Then you select "use 0000", click next, what do you get? "Enter 518421 at the other device." :(

Then you select "use custom pin", enter 0000 yourself, click next. "Enter 518421 at the other device.". It just doesn't care what the user wants.

Where is the upstream place to report this? It has been here for years and it is really time for it to go away.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
Bobby Patten (limon160) wrote :

I installed "Blueman Bluetooth Manager" and am able to connect my devices. I think this is just a different front end to the Bluez Backend.

This makes me think the problem we are have is in the GUI.

also while i was trying to track this down i noticed the file "/etc/init/bluetooth.conf" line 8 "env UART_CONF=/etc/bluetooth/uart", uart does not exist as a file or directory. This may be nothing, but thought it was odd.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers