Synaptics touchpad ceases functioning after suspend and resume.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Invalid
|
Undecided
|
Unassigned | ||
cruft (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
After suspending the notebook, resume works fine except that the Synaptics touchpad no longer responds to any input.
Restarting the X server does not help.
Attempting to cat /dev/input/mice at the console and then moving the touchpad does not show any input being received. The touchpad which had been /dev/input/mouse0 is no longer listed after the resume.
This bug was present in Dapper and still exists in the current (2006-09-11) build of Edgy as well and Karmic Koala (9.10)
Gateway MX6625 Notebook
Centrino Chipset
Synaptics Touchpad
Also affects
Gateway MX6025 Notebook with Karmic Koala 9.10
HP EliteBook 2530p with Ubuntu Lucid 10.04 LTS amd64
Fujitsu Siemens Computer Aminlo Si1520 with Ubuntu Lucid 10.04 LTS
and others.
Multiple ways to bypass the bug are suggested in comments. Adding Grub parameter atkbd.reset worked for many. Set GRUB_CMDLINE_
Changed in linux-source-2.6.20: | |
assignee: | nobody → timg-tpi |
Changed in linux-source-2.6.20: | |
assignee: | timg-tpi → ubuntu-kernel-acpi |
importance: | Undecided → Low |
status: | Needs Info → Confirmed |
Changed in linux-source-2.6.24: | |
status: | New → Invalid |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux-source-2.6.20: | |
status: | Confirmed → Won't Fix |
description: | updated |
description: | updated |
description: | updated |
Changed in linux-source-2.6.20 (Ubuntu): | |
assignee: | Registry Administrators (registry) → nobody |
Not sure that I agree with assigning this bug as belonging to xserver- xorg-input- synaptics. The fact that the touchpad no longer shows up in /dev/input/ would suggest to me that the problem is lower level than the X server.
I'm no expert on the matter, however, so I could certainly be wrong. :-)