** Also affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New
** Changed in: utouch Status: In Progress => Invalid ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Assignee: (unassigned) => Chase Douglas (chasedouglas) ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided => Medium ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New => In Progress ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Milestone: None => ubuntu-10.10 ** Description changed: - When the synaptics driver is called, it looks for the first touchpad - that isn't already handled by synaptics. This is wrong in so many ways, - especially when, for example, it grabs the magic trackpad that's driven - by evdev when it was really looking for the normal trackpad on the - laptop. - - Synaptics must be stopped! + Two touchpad devices A and B + X enumerates A before B + They both have a /dev/input/event* node and a /dev/input/mouse* node + I set up xorg.conf to use evdev for A + A gets handled by evdev + B's /dev/input/mouse* node gets probed by synaptics + it doesn't match /dev/input/event* in the synaptics probe function, so synaptics runs the eventcomm AutoDevProbe callback + the AutoDevProbe callback finds the first evdev node that isn't grabbed by synaptics already + in this case, it finds A and grabs it -- xserver-xorg-input-synaptics grabs devices it shouldn't https://bugs.launchpad.net/bugs/624985 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp