'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'

Bug #1961581 reported by Naman Kumar Bhalla
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-signed-hwe-5.13 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Touchpad used to work fine initially but I recently realised that it's not responding at all, since I'm mostly working with an external mouse. Therefore, I'm not sure when this problem started or what really caused it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 21 12:13:55 2022
InstallationDate: Installed on 2021-11-02 (111 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Naman Kumar Bhalla (nkbhalla) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-hwe-5.13 (Ubuntu):
status: New → Confirmed
Revision history for this message
Alexander (aletschius) wrote :

Hi this could be a issue of Fujitsu Laptops in general, i have propably the same problem just on a different laptop model.

I did issue a similar bug report, because it's a different model, but i think its definitely possible, that this bug is connected to the touchpad that Fujitsu uses in general respectively the manufacturer.

If you did find a fix, pleas tell me then i will try it on my model as well.

With best regards,
Alexander

Revision history for this message
Alexander (aletschius) wrote :

My bug report is this one:

https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1963554

just for the sake of completeness.

Revision history for this message
Naman Kumar Bhalla (nkbhalla) wrote :

@aletschius For me, running:
“sudo modprobe i2c-hid-acpi”
on the terminal worked.

To avoid running this after every log-in, just add:
“i2c-hid-acpi”
in a new line to:
“/etc/modules”

Revision history for this message
Alexander (aletschius) wrote :

Thanks for that workaround “i2c-hid-acpi” definitely worked so after next reboot "/etc/modules" will work propably too.

Thanks again

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.