[Bug 585592] [NEW] Bluetooth PIN always random

co0lingFir3 co0lingFir3 at googlemail.com
Tue May 25 22:20:52 BST 2010


Public bug reported:

Binary package hint: bluez

Hello,

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 2.6.32.11+drm33.2
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
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
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.
hciconfig:
 hci0:	Type: USB
 	BD Address: 00:22:43:FD:5C:E3 ACL MTU: 1021:8 SCO MTU: 64:1
 	UP RUNNING PSCAN 
 	RX bytes:1007 acl:0 sco:0 events:33 errors:0
 	TX bytes:1103 acl:0 sco:0 commands:33 errors:0

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 lucid

-- 
Bluetooth PIN always random
https://bugs.launchpad.net/bugs/585592
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in ubuntu.



More information about the Ubuntu-bluetooth mailing list