Problems pairing Apple's Magic trackpad in 13.10

Bug #1251637 reported by Ed Bakker on 2013-11-15
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

Hereby the requested bug report!
===========================

Despite having search in the answers about pairing (problems with) Apple's Magic trackpad and having run through:

https://wiki.ubuntu.com/Multitouch/AppleMagicTrackpad

If you find that you are not being prompted to "Always grant access" and that the device is not available after a reboot (i.e., you have to reconnect), try adding the pincode for the device (0000) to /var/lib/bluetooth/<physical_device_ID>/pincodes, like so:

In a terminal:

Determine the physical (model-specific) and unique device IDs from the output of lsinput (from the "input-tools" package) as shown above.

Create /lib/bluetooth/<physical_ID>/pincodes as the root user (or with sudo):

 # This folder *should* already exist, create it with 'sudo mkdir' if not.
 # You can use TAB to complete, if it's the only Bluetooth device on your system:
 cd /lib/bluetooth/<physical_ID>

 sudo gedit pincodes
Add this line to the new file, save, and exit:
 <unique_ID> 0000
where <physical_ID> is a backslash-escaped physical device ID, like D8\:30\:62\:38\:18\:02, and <unique_ID> is your device's unique ID, both from the output of lsinput.

I don't get to succeed in pairing, let alone 'automatic pairing at login' of the Apple's trackpad!
Each time it tells me it failed!
Also it's strange to see that Apple's trackpad is recognized as 'tablet' and not as 'input device', seen the 'automatic pin' of 0000 should be filled in automatically. Whatever I do; it refuses to pair!

Can something be done about this? Until now in 13.10 I've (re)paired the trackpad (in dualboot 13.10 to OSX) each single time after login! There should be another (automatic) way I think....

Kind regards,

Ed

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1251637/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu:
status: New → Confirmed
Ed Bakker (ed-r-bakker) wrote :

Extra info:

The pair requests from the Apple Magic trackpad "are seen" by Ubuntu 13.10; both within Unity, Gnome and also in Cinnamon 2.0!

A 'pairing-request-fill-in-pincode" DOES appear, but it does NOT let you the time nor the possibility to fill in '0000'; by that time the small screen is long gone again.... Each time the trackpad sends out a pairing-request this small 'pin-screen' does appear but one is not able to fill in the pin...

Also... the trackpad is detected as 'tablet'; not as 'input device' which is wrong.
And ... the automatic pin '0000' option for input devices, once chosen, does NOT fill in this very pin either upon pairing request!
It's a real nuisance as for other, earlier versions I've been pairing manually each and every time!! Which should not be necessary as OSX pairs automatically!

And, when the trackpad had been used in OSX, restarting directly into Ubuntu 12.04 at the time, pairing failed as well.
I have the impression once it's warm rebooted, it does not pair either! Cold reboots in the past with earlier versions DID let me (manually) pair it! Never warm reboots succeeded either; as if the trackpad was still 'seen' by the (hardware) side of things!

Hope this clarifies the bug also a bit!

Ed Bakker (gaytan) wrote :

To the question asked by you permail:

Your question #240179 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/240179

    Status: Open => Needs information

actionparsnip requested more information:
Ok if you set the device to discoverable and run:

sudo hcitool scan

Do you get the device detected?

The result output is:

gaytan@MMUG:~$ sudo hcitool scan
[sudo] password for gaytan:
Scanning ...
gaytan@MMUG:~$ sudo hcitool scan
Scanning ...
gaytan@MMUG:~$

Within the OSX side (Mavericks) all is working fine!!

Ed Bakker (gaytan) wrote :
Download full text (3.4 KiB)

the command you are looking for is: 'sudo lsinput'

It's output:

gaytan@MMUG:~$ sudo lsinput
/dev/input/event0
   bustype : BUS_HOST
   vendor : 0x0
   product : 0x1
   version : 0
   name : "Power Button"
   phys : "PNP0C0C/button/input0"
   bits ev : EV_SYN EV_KEY

/dev/input/event1
   bustype : BUS_HOST
   vendor : 0x0
   product : 0x3
   version : 0
   name : "Sleep Button"
   phys : "PNP0C0E/button/input0"
   bits ev : EV_SYN EV_KEY

/dev/input/event2
   bustype : BUS_HOST
   vendor : 0x0
   product : 0x1
   version : 0
   name : "Power Button"
   phys : "LNXPWRBN/button/input0"
   bits ev : EV_SYN EV_KEY

/dev/input/event3
   bustype : BUS_HOST
   vendor : 0x0
   product : 0x6
   version : 0
   name : "Video Bus"
   phys : "LNXVIDEO/video/input0"
   bits ev : EV_SYN EV_KEY

/dev/input/event4
   bustype : BUS_USB
   vendor : 0x47d
   product : 0x2048
   version : 273
   name : "Primax Kensington Eagle Trackbal"
   phys : "usb-0000:00:14.0-2/input0"
   uniq : ""
   bits ev : EV_SYN EV_KEY EV_REL EV_ABS EV_MSC

/dev/input/event5
   bustype : BUS_USB
   vendor : 0x5ac
   product : 0x250
   version : 273
   name : "Apple Inc. Apple Keyboard"
   phys : "usb-0000:00:14.0-3.2/input0"
   uniq : ""
   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

/dev/input/event6
   bustype : BUS_USB
   vendor : 0x5ac
   product : 0x250
   version : 273
   name : "Apple Inc. Apple Keyboard"
   phys : "usb-0000:00:14.0-3.2/input1"
   uniq : ""
   bits ev : EV_SYN EV_KEY EV_MSC

/dev/input/event9
   bustype : (null)
   vendor : 0x0
   product : 0x0
   version : 0
   name : "HDA Intel PCH HDMI/DP,pcm=8"
   phys : "ALSA"
   bits ev : EV_SYN EV_SW

/dev/input/event10
   bustype : (null)
   vendor : 0x0
   product : 0x0
   version : 0
   name : "HDA Intel PCH HDMI/DP,pcm=7"
   phys : "ALSA"
   bits ev : EV_SYN EV_SW

/dev/input/event11
   bustype : (null)
   vendor : 0x0
   product : 0x0
   version : 0
   name : "HDA Intel PCH HDMI/DP,pcm=3"
   phys : "ALSA"
   bits ev : EV_SYN EV_SW

/dev/input/event12
   bustype : (null)
   vendor : 0x0
   product : 0x0
   version : 0
   name : "HDA Intel PCH SPDIF In"
   phys : "ALSA"
   bits ev : EV_SYN EV_SW

/dev/input/event13
   bustype : (null)
   vendor : 0x0
   product : 0x0
   version : 0
   name : "HDA Intel PCH Headphone"
   phys : "ALSA"
   bits ev : EV_SYN EV_SW

/dev/input/event14
   bustype : (null)
   vendor : 0x0
   product : 0x0
   version : 0
   name : "HDA Intel PCH Line"
   phys : "ALSA"
   bits ev : EV_SYN EV_SW

/dev/input/event15
   bustype : BUS_USB
   vendor : 0x5ac
   product : 0x8242
   version : 273
   name : "Apple, Inc. IR Receiver"
   phys : "usb-0000:00:1d.0-1.8.2/input0"
   uniq : ""
   bits ev : EV_SYN EV_KEY EV_REP

/dev/input/event16
   bustype : BUS_USB
   vendor : 0xc45
   product : 0x6340
   version : 0
   name : "USB 2.0 Camera"
   phys : "usb-0000:00:14.0-4/button"
   bits ev : EV_SYN EV_KEY

NO Apple Magic Trackpad showing in the list.... With my former iMac it DID appear in the list as example given on:
(XX values filled in for real values of course...!)

https://wiki.ubunt...

Read more...

Ed Bakker (gaytan) wrote :

In my xorg.conf has already been added (by myself):

Section "InputClass"
    Identifier "Apple Magic Trackpad"
    MatchIsTouchpad "on"
    MatchUSBID "05ac:030e"
    Driver "Synaptics"
    Option "VertScrollDelta" "50"
    Option "HorizScrollDelta" "50"
    Option "MinSpeed" "0.6"
    Option "MaxSpeed" "2.5"
    Option "AccelFactor" "1.0"
    Option "ZAxisMapping" "5 4"
    Option "TapButton1" "1"
    Option "VertEdgeScroll" "1"
    Option "EmulateTwoFingerMinZ" "29"
    Option "EmulateTwoFingerMinW" "5"
    # these two options are for multiple monitors 3:1 ratio.
EndSection

Ed Bakker (gaytan) wrote :

Also the /lib/bluetooth/mac_addres/pincodes already has been created, with value: C8:BC:C8:F5:FE:55 0000

Despite that; not being able to pair!!

It's curious to see found articles going back to 2010, stating exact the same problems! Ever since 'nothing' / 'not enough' has been done about it to really solve this issue:

https://www.google.com/cse?cx=002683415331144861350%3Atsq8didf9x0&q=ubuntu+pair+apple+magic+trackpad&ie=UTF-8&sa=Search#gsc.tab=0&gsc.q=ubuntu%20pair%20apple%20magic%20trackpad&gsc.page=1

It's nothing new really and yet the latest Ubuntu version is STILL NOT able to do a simple thing as pairing an Apple Magic trackpad; also many bugs exist right this moment in Launchpad, people having similar problems not being able to get their (Apple or other brand) trackpad(s) going....

I wonder if this 'trackpad feature' will ever be solved really....

glass.dimly (jmjohn) wrote :

lsinput doesn't work for me because... the system doesn't recongnize my device. `hidd` didn't work for me in 14.04 (Trusty).

I partially followed instructions from here: http://www.acim.net/archives/119

    sudo apt-get install blueman
    blueman-manager

blueman-manager got the underlying bluez utility to recognize it, at which point there was an entry for it in the regular ubuntu bluetooth menu. In the dropdown configuration for the Trackpad, I had to switch it to "on."

Then it worked and was configurable.

Jeff Pihach (hatch) wrote :

The solution mentioned in #8 was the only way I've been successful in getting the device to pair.

this is on debian jessie: i've managed to pair it using blueman, or at least it looked like that, but it did not move my pointer... :/

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

Other bug subscribers