I experimented with the module synaptic editing its code hoping to fix it myself. It seemed to me that the incorrect behaviour was already present in codes passed on to synaptics_parse_hw_state(...). BTW, the touchpad works fine under Windows which eliminates the explanation that touchpad firmware or the hardware is faulty.
I experimented with the module synaptic editing its code hoping to fix it myself. It seemed to me that the incorrect behaviour was already present in codes passed on to synaptics_ parse_hw_ state(. ..). BTW, the touchpad works fine under Windows which eliminates the explanation that touchpad firmware or the hardware is faulty.