Turns this seems to be caused by a disabled AbstractButton that still produces haptics feedback even though its disabled.
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1300709 Title: Empty areas in scopes produce haptics feedback without triggering any other action Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: If a scope category contains a uneven amount of items (in a sense that its not evenly divisible by columnCount) it leaves a bit of empty space at the lower right corner. Tapping into that area doesn't do anything but still produces haptics feedback. Such a feedback should only be used when there's actually an action triggered by the tap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1300709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp