Bluetooth PIN always random

Bug #585592 reported by co0lingFir3
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Undecided
Unassigned
gnome-bluetooth (Ubuntu)
Expired
High
Unassigned

Bug Description

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

Revision history for this message
co0lingFir3 (coolingfire) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
Revision history for this message
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.

Revision history for this message
dobey (dobey) wrote :

This issue still exists on 14.04.

Changed in gnome-bluetooth (Ubuntu):
importance: Undecided → High
tags: added: trusty
removed: lucid
Revision history for this message
Rical (aricim) wrote :

In Ubuntu 14.04 LTS updated each day, on ASUS N56JR, one year old.

Some weeks ago, I seen many updates about devices which give me some progress.
And I thank you very much.
Before, bluetooth never appears. After, I have bluetooth once on two reboots, but not exactly 1/2. If I needs it and that I don't have it, I can reboot once or twice and have it.

Some seconds before the end of bios boot time, there is a display shorter than one second, not always the same shape.
At the end of bios boot time, during 3 seconds the display is one of:
B0 - none messages.
B1 - 1 message starting with: "device"
B2 - 2 messages starting with: "Bluetooth"

Today I had B2 boot, and now I see the Bluetooth menu and its peripherals.
The Bluetooth menu icon is grey and not lighting.

glogg traces selecting "luet":
Dec 30 10:39:51 N56JR-UBU bluetoothd[818]: Adapter /org/bluez/818/hci0 has been disabled
Dec 30 10:39:51 N56JR-UBU bluetoothd[818]: Unregister path: /org/bluez/818/hci0
Dec 30 10:39:51 N56JR-UBU bluetoothd[818]: Endpoint unregistered: sender=:1.62 path=/MediaEndpoint/A2DPSink
Dec 30 10:39:51 N56JR-UBU bluetoothd[818]: Endpoint unregistered: sender=:1.62 path=/MediaEndpoint/A2DPSource
Dec 30 10:39:51 N56JR-UBU bluetoothd[818]: Endpoint unregistered: sender=:1.62 path=/MediaEndpoint/HFPAG
Dec 30 10:39:51 N56JR-UBU bluetoothd[818]: Endpoint unregistered: sender=:1.62 path=/MediaEndpoint/HFPHS
Dec 30 10:39:51 N56JR-UBU kernel: [ 4552.558704] usb 3-5: Product: Bluetooth USB Host Controller
Dec 30 10:39:54 N56JR-UBU kernel: [ 4555.559615] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096
Dec 30 10:39:54 N56JR-UBU kernel: [ 4555.559624] Bluetooth: Loading patch file failed

glogg traces selecting "evice" without NetworkManager:
Dec 30 10:39:51 N56JR-UBU kernel: [ 4549.207043] PM: suspend of devices complete after 1077.530 msecs
Dec 30 10:39:51 N56JR-UBU kernel: [ 4549.222990] PM: late suspend of devices complete after 15.932 msecs
Dec 30 10:39:51 N56JR-UBU kernel: [ 4549.271425] PM: noirq suspend of devices complete after 48.393 msecs
Dec 30 10:39:51 N56JR-UBU kernel: [ 4550.187222] PM: noirq resume of devices complete after 118.998 msecs
Dec 30 10:39:51 N56JR-UBU kernel: [ 4550.187333] PM: early resume of devices complete after 0.090 msecs
Dec 30 10:39:51 N56JR-UBU kernel: [ 4550.187423] nouveau [ DRM] re-enabling device...
Dec 30 10:39:51 N56JR-UBU kernel: [ 4550.507502] usb 3-5: reset full-speed USB device number 6 using xhci_hcd
Dec 30 10:39:51 N56JR-UBU kernel: [ 4550.523631] usb 3-5: device firmware changed
Dec 30 10:39:51 N56JR-UBU kernel: [ 4552.368493] PM: resume of devices complete after 2179.397 msecs
Dec 30 10:39:51 N56JR-UBU kernel: [ 4552.368748] usb 3-5: USB disconnect, device number 6
Dec 30 10:39:51 N56JR-UBU kernel: [ 4552.541047] usb 3-5: new full-speed USB device number 7 using xhci_hcd
Dec 30 10:39:51 N56JR-UBU kernel: [ 4552.558700] usb 3-5: New USB device found, idVendor=13d3, idProduct=3362
Dec 30 10:39:51 N56JR-UBU kernel: [ 4552.558703] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

co0lingFir3,

Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached EOL on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please upgrade to the latest version and re-test.

Changed in gnome-bluetooth (Ubuntu):
status: Confirmed → Incomplete
Changed in bluez (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-bluetooth (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.