Package Details: xf86-input-mtrack-git 0.3.1.r1.g56f9831-1

Git Clone URL: https://aur.archlinux.org/xf86-input-mtrack-git.git (read-only)
Package Base: xf86-input-mtrack-git
Description: A multitouch X driver using the kernel MT protocol
Upstream URL: http://github.com/BlueDragonX/xf86-input-mtrack
Licenses: GPL
Conflicts: xf86-input-mtrack, xf86-input-synaptics
Provides: xf86-input-mtrack
Submitter: mikezackles
Maintainer: mikezackles
Last Packager: mikezackles
Votes: 29
Popularity: 0.731736
First Submitted: 2011-04-26 16:31
Last Updated: 2015-10-24 13:48

Latest Comments

gsora commented on 2016-03-04 15:17

The Upstream URL is not correct, please modify it accordingly.

viniavila commented on 2016-02-23 16:48

I don't know what to do.

I've installed this package to use mtrack instead of synaptics in my bcm5914 trackpad (Macbook Air 2012) But Xorg insists not to load the mtrack module!

[vinicius@MacBookAir ~]$ cat /var/log/Xorg.0.log | grep "(EE)"
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 5.223] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 5.223] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 7.140] (EE) mtrack: cannot configure device
[ 7.140] (EE) Couldn't init device "bcm5974"

I already added my user to input group which is useless since this problem is recorded BEFORE logon in lightdm (I'm using lightdm-gtk-greeter). I tried many settings within 10-mtrack.conf found in internet but none worked. Few days ago in another arch intallation I could make this work flawlessly so I can't figure out what am i doing wrong... Some help wold be appreciated...

mikezackles commented on 2015-10-24 13:52

Thanks epinephrine. I've switched over to p2rkw's fork. Just let me know if anyone has issues, and I'll switch it back.

epinephrine commented on 2015-10-22 21:56

Looking at the fork network (https://github.com/BlueDragonX/xf86-input-mtrack/network), I noticed that apparently p2rkw continues development. I got in touch with him and he confirmed that BlueDragonX doesn't work on the project at the moment and that he continues development.

So maybe we should change the upstream and source url to https://github.com/p2rkw/xf86-input-mtrack?

mikeokner commented on 2015-08-17 23:03

I'm running into some issues trying to use this driver on a MacBook Pro 11,5 (mid-2015 with Force Trackpad). I tried using both mtrack and synaptics with the latest available kernel via pacman (4.1.5-1) to no avail. Both resulted in an unresponsive cursor -- clicking worked, though. Only the evdev driver worked, but then I didn't have two-finger scrolling or right clicking.

I updated to linux-mainline available via AUR (4.2rc7-1) after seeing a note in the Macbook wiki page. The synaptics driver does work now under 4.2, but the mtrack driver still results in an unresponsive cursor. I'd love to get mtrack working if possible.

mikezackles commented on 2015-07-05 06:13

Thanks for the feedback all. I've added a post_install message that points out the location of the config file and suggests adding yourself to the input group. I've also added xf86-input-synaptics as a conflict.

boterock commented on 2015-07-05 01:55

It should be noted somewhere that the config is in /usr/share/X11/xorg.conf.d/...
I spent my last four days followin internet docs that referred the config file in /etc/X11/xorg.conf.d, and I only realized the config file is in /usr/share because in the comments there is a link to a git diff where I found the config URL

liskevich commented on 2015-05-22 15:18

@hobarrera - I had same issue all of a sudden on my Macbook Pro. You need to add yourself to the input user group so:
sudo gpasswd -a <Yourusername> input

Then just reboot and enjoy

hobarrera commented on 2015-05-14 00:37

Nor this package, nor xf86-input-mtrack worked for me on a 2013 macbook air. No errors on Xorg.0.log. Does anyone else have similar experience on this same hardware?

jyantis commented on 2015-04-20 14:37

Just tested it. Seems to work fine though I did have to remove xf86-input-synaptics to get it to work properly.

All comments