Touchpad not working completely.

Bug #1855645 reported by GShyam
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The touchpad stopped working suddenly. At night of yesterday, it was working, but in the morning it was not worked. Before its stop working there were some packages showing there update and asking for the restart of the system. And did not restart that time. After some time I shutdown my system. But after starting the system the came in the touchpad. My system working in dual boot mode with windows 10 also. Touchpad working in the windows 10.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-72-generic 4.15.0-72.81
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0p: ghanshyam 1675 F...m pulseaudio
 /dev/snd/controlC1: ghanshyam 1675 F.... pulseaudio
 /dev/snd/controlC0: ghanshyam 1675 F.... pulseaudio
CRDA:
 global
 country IN: DFS-UNSET
  (2402 - 2482 @ 40), (N/A, 20), (N/A)
  (5150 - 5350 @ 160), (N/A, 23), (N/A)
  (5725 - 5875 @ 80), (N/A, 23), (N/A)
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 9 09:57:19 2019
InstallationDate: Installed on 2019-01-28 (314 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Vostro 3558
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=c754d81b-93d5-449d-aa12-40e76d829be9 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-72-generic N/A
 linux-backports-modules-4.15.0-72-generic N/A
 linux-firmware 1.173.12
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0PPH4M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0PPH4M:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Vostro 3558
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
GShyam (ghanshyam99) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

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

Probable duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798
"Synaptics, product: TM3108-002" (that report impacts Synaptics s3203 and TM2714-002)

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
GShyam (ghanshyam99) wrote :

Sorry, but I did not get the solution.
Can you explain the solution a little bit?
And why this happened and what is this bot?

Revision history for this message
Chris Guiver (guiverc) wrote :

I suggest looking at the aforementioned link (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798), and trying what has been suggested there (eg. comment 13 OR 15).

If you try it, and it works PLEASE report back here or on other 1854798 bug report. (this report can be marked a duplicate of the other one; ie. same problem with same fix)

The 'fix' (a reversion) has been found to work on the other s3203/TM2714-002 as noted in the other bug report I linked.

Bots are not people, it's a program running on a machine that looked through your provided files & 'confirmed' at least one other user has the same issue (recorded in their logs). It adds 'heat' to your bug (you'll note the 'heat' for the other report is much higher, it'll thus get more attention).

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hi GShyam,
This issue looks like a duplicate of bug 1854798, you can try the suggestions there, or just boot with an older kernel before the kernel update (e.g. 4.15.0-70). If you think this is not the same issue, please feel free to change the bug status.

Thank you.

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.