Interesting to see the button events using the command "xinput test bcm5974"... With Unity loaded the middle click (three fingers) is reported incorrectly as button #1 being pressed and released. Without Unity, xinput correctly reports the middle click as button #2.
Also note that without Unity in Ubuntu Classic (not effects), I can reintroduce the bug by running "geistest" at the same time as the above xinput test (in different windows). So it would seem that libutouch-geis might be close the cause.
Interesting to see the button events using the command "xinput test bcm5974"... With Unity loaded the middle click (three fingers) is reported incorrectly as button #1 being pressed and released. Without Unity, xinput correctly reports the middle click as button #2.
Also note that without Unity in Ubuntu Classic (not effects), I can reintroduce the bug by running "geistest" at the same time as the above xinput test (in different windows). So it would seem that libutouch-geis might be close the cause.