Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1854896

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Possible duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854895
With apport details not being provided, it's harder to tell

However this is not Ubuntu, thus have Mint changed anything in the stack at that level that changes things?

its not mint issue its kernel issue and that's definitely confirmed. it happened after updating to the latest kernel

also after running the above command i am getting this

$ apport-collect 1854896
ERROR: The python3-launchpadlib package is not installed. This functionality is not available.

Can you please find out the last working kernel version?

Apport tools are installed by default on Ubuntu systems, you'll need to install it to get it to run on Linux Mint.

(fyi: answering @kaihengfeng's question is more important!)

I also had this problem. Touchpad stopped working after installation of Kernal 4.15.0-72, working fine after reverting to Kernal 4.15.0-70.
Kernal intstalled using linux mint update manager, and removed again with update manager.

Although I occasionally use the terminal, I am an ex Windows user and find the Gui packages easier to use.
Laptop is a Dell Inspiron 15 3000 series - running Linux Mint 18.3 and Windows 10 in dual boot configuration.

This hit me today on Ubuntu 18.04. Upgraded to kernel 4.15.0-72-generic and the touchpad does not move. The touchpad *buttons* do work, but I cannot move the cursor. Booting in to 4.15.0-70-generic makes them work again.

I tried running apport-collect 1854896 but it says I can't do so because I'm not the owner of the bug.

Note, I'm running vanilla Ubuntu 18.04.3, *not* Mint.

Thank you Alex Cabal (acabal).

I'd suggest you look at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854895 and click 'bug affects me too' IF that report seems to apply. That report isn't missing detail and has a greater chance of being acted on.

If however the report I'm suggesting doesn't apply, you could file your own bug report with `ubuntu-bug` and I can make this a duplicate of yours (thus this report will become the confirmation).

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I have a same problem after installation of Kernal 4.15.0-72.
The Kernel was installed using Linux Mint update manager.
Laptop is a Dell Inspiron I14-3442-a10 - running Linux Mint 19.2

same issue with not working Touchpad - Synaptics TM3336-002 - using kernel: 4.15.0-72-generic #81~16.04.1-Ubuntu

Back to kernel 4.15.0-70 works just fine.

Same issue with

  - Touchpad: Synaptics s3203
  - kernel : 4.15.0-72-generic
  - Distro : Kubuntu 18.04

Back to kernel 4.15.0-70 works just fine.

Same problem here with Synaptics TM3336-002 using kernel: 4.15.0-72.

How can I go back to kernel 4.15.0-70 ?

Same issue happening in my laptop after kernel update 4.15.0-72 i have dell 3542 , i am sure problem in kernel i move to linux mint cause i face touchpad not working in ubuntu 16.4.6 after updating kernel and now same happens to linux mint

Follow this steps, it works for me:

1. Run
    $ sudo -H gedit /etc/default/grub

In the open window edit line

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

it should look this way

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"

Save file and run

    $ sudo update-grub

2. Run
    $ echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf
    $ sudo depmod -a
    $ sudo update-initramfs -u
    $ echo "synaptics_i2c" | sudo tee -a /etc/modules

3. Reboot.

Tank you very much Nilesh, this solution was the perfect fix for me!

The solution given by Nilesh worked for me too.