Comment 0 for bug 1518737

I am running Ubuntu 15.10 (32-bit edition but I know it is also a problem on 64-bit edition) on an Acer Aspire 5738 laptop which has a physical button next to the touchpad that can toggle the device.
When I hit the button a desktop notification appears, informing me that the device has been disabled (an icon of a touchpad with an x in the bottom-right-hand-corner) and I am no longer able to use the touchpad for anything, as expected.
When I press the button again to re-enable the touchpad, a desktop notification appears, informing me that the device has been enabled (an icon of a touchpad with no x in the bottom-right-hand-corner) but the touchpad remains disabled, i.e I can use it for absolutely nothing. (clicking, scrolling, pointing, ...)
Logging in and out or restarting the PC enables the touchpad, but I can also use modprobe to remove and insert psmouse module, which will also cause it to enable.
When I use the button physically next to the touchpad to enable/disable the touchpad, it does not affect the toggle switch in the "Mouse and Touchpad" settings, but if I use that setting (the toggle switch) I can correctly enable and disable the touchpad.
xinput lists the device under "Virtual core pointer" as an "AlpsPS/2 ALPS GlidePoint".
BIOS is updated as of today.
If I can be of help in patching the bug, I would love to, but I just have no idea where to look. I altered the psmouse kernel module to print information to the logs about various activity (resetting, deactivating) but none of it was very informative (again, I don't know where to look).