← Back to team overview

kernel-packages team mailing list archive

[Bug 618838] Re: Apple Magic Trackpad requires PIN to pair, fails manual pairing

 

I've noticed that the pairing assistant wizard remembers the PIN option specified when run as root.
I read on the GNOME blog that GNOME 3.10 will have completely re-done Bluetooth wizard, so this issue (which I'm also experiencing) may be resolved then. I've installed `blueman` in the interim which is an alternative GTK+ bluetooth management utility for GNOME using the bluez D-Bus backend.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/618838

Title:
  Apple Magic Trackpad requires PIN to pair, fails manual pairing

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: bluez

  The Apple Magic Trackpad requires a PIN to pair upon first activation.
  Such PIN is '0000' which can be entered on a regular keyboard. Once
  connected, it also requires granting authorization to connect again.
  See the two attachments for such dialogs.

  When trying to setup this device manually (after moving it from
  another system, for example), by default Ubuntu will propose a random
  6-number PIN, which can't be entered on the trackpad, which then means
  pairing fails.

  This trackpad should connect automatically, although I don't
  personally know enough about bluetooth to suggest how this should
  happen.

  I have documented a workaround to pair this device here:
  https://wiki.ubuntu.com/Multitouch/AppleMagicTrackpad

  Once paired the device does not need pairing each time the system is
  used / restarted, it will remember it.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
  Uname: Linux 2.6.35-15-generic i686
  Architecture: i386
  Date: Mon Aug 16 15:24:53 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100812)
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: Acer Aspire R1600
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-15-generic root=UUID=30841bc6-7bfc-4ffb-8b7c-60772f799265 ro nosplash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: bluez
  dmi.bios.date: 06/17/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FMCP7A-ION
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A1:bd06/17/2009:svnAcer:pnAspireR1600:pvr:rvnAcer:rnFMCP7A-ION:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire R1600
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:	Type: BR/EDR  Bus: USB
   	BD Address: 00:0F:3D:3D:7C:5C  ACL MTU: 192:8  SCO MTU: 64:8
   	UP RUNNING PSCAN 
   	RX bytes:7619 acl:369 sco:0 events:124 errors:0
   	TX bytes:551 acl:12 sco:0 commands:50 errors:0
  rfkill:
   0: hci0: Bluetooth
   	Soft blocked: no
   	Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/618838/+subscriptions