When the touchpad is disabled via hotkey it will not respond when brought back on by pressing the key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-synaptics (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: xserver-
This is a Acer Aspire 7540, the key does light up and ubuntu seems to know that I have disabled the pad and turned it back on, however it will not respond after turning it on... even though ubuntu shows the touchpad icon without an x and the light does turn off, a restart is required to enable the touchpad after doing so.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Mon Oct 4 18:00:27 2010
DkmsStatus: fglrx, 8.723.1, 2.6.32-25-generic, x86_64: installed
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: Acer Aspire 7540
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: xserver-
dmi.bios.date: 08/14/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.07
dmi.board.name: JV71TR
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Aspire 7540
dmi.product.
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-25-generic
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
importance: | Undecided → Low |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
status: | New → Incomplete |
status: | Incomplete → New |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
importance: | Low → Undecided |
summary: |
- when the touchpad is disabled via hotkey it will not respond when + When the touchpad is disabled via hotkey it will not respond when brought back on by pressing the key |
Changed in xserver-xorg-input-synaptics (Ubuntu): | |
importance: | Undecided → Low |
Status changed to 'Confirmed' because the bug affects multiple users.