touchpad cursor frozen (does not move) after suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: xserver-
When I go to suspend and then resume back the touchpad cursor becomes frozen and the touchpad thus becomes unusable. I tested it when running on battery power and with no mouse attached. (However it may behave in the same way also under other conditions.)
I must add that I was getting the same bug (and reported or commented it long time ago) also for the Intrepid Ibex version of ubuntu which I have had installed on the same machine until recently. (The machine is a 32-bit notebook with an Intel 945 GM chipset. Currently I am using ubuntu 10.04 LTS. Visual effects are switched off.)
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Mon May 31 18:09:36 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: FUJITSU SIEMENS AMILO Pro V3205
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: xserver-
dmi.bios.date: 02/14/2007
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.20
dmi.board.name: 10AD
dmi.board.vendor: FUJITSU
dmi.board.version: 03
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.
dmi.modalias: dmi:bvnPhoenix:
dmi.product.name: AMILO Pro V3205
dmi.product.
dmi.sys.vendor: FUJITSU SIEMENS
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-22-generic
affects: | xserver-xorg-video-intel (Ubuntu) → linux (Ubuntu) |
tags: | added: resume suspend |
Changed in linux (Ubuntu): | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
tags: | added: kernel-power |
Hi Martin,
If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]