The mtrack driver is not well maintained (and not maintained at freedesktop.org like the other drivers) so it is not something we want to include in -input-all. For this hardware we recommend using the -synaptics driver, which is better maintained.
That said, despite the maintenance problems mtrack does have a few features that -synaptics lacks currently, so we're ok leaving it in the repositories for users to optionally install at their discretion. However, since -mtrack is maintained separately from the rest of the X stack, when we update the X stack it will need to be updated as well, and may fail to build until then, so if it's mentioned in your xorg.conf your system may fail to boot properly; this is probably the root cause of the issue you encountered. Robert mentioned the driver is building now so perhaps the problem has resolved itself.
Ultimately, whatever features -mtrack provides need to be incorporated into either the -evdev or -synaptics driver.
Hi Clint,
The mtrack driver is not well maintained (and not maintained at freedesktop.org like the other drivers) so it is not something we want to include in -input-all. For this hardware we recommend using the -synaptics driver, which is better maintained.
That said, despite the maintenance problems mtrack does have a few features that -synaptics lacks currently, so we're ok leaving it in the repositories for users to optionally install at their discretion. However, since -mtrack is maintained separately from the rest of the X stack, when we update the X stack it will need to be updated as well, and may fail to build until then, so if it's mentioned in your xorg.conf your system may fail to boot properly; this is probably the root cause of the issue you encountered. Robert mentioned the driver is building now so perhaps the problem has resolved itself.
Ultimately, whatever features -mtrack provides need to be incorporated into either the -evdev or -synaptics driver.