cursor frozen after screen unlock on acer aspire one D260

[James Hunt]

I performed a fresh install of oneiric desktop on an Acer Aspire One D260. Screensaver kicked in and I then unplugged from AC power and unlocked the screen.

Result: Unity and X appeared to be working (keyboard is responsive, but cursor is frozen.

I installed input-utils, mtdev-test and gpm and established that:

- synaptic touchpad events are being received
- the gpm mouse cursor works perfectly

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-input-synaptics 1.4.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Wed Oct 12 10:48:58 2011
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
MachineType: Acer AOD260
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=87989852-317c-4a8c-83fd-b52ba920236d ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: AOD260
dmi.board.vendor: Acer
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.01
dmi.modalias: dmi:bvnAcer:bvrV1.01:bd04/28/2010:svnAcer:pnAOD260:pvrV1.01:rvnAcer:rnAOD260:rvrV1.01:cvnAcer:ct10:cvrV1.01:
dmi.product.name: AOD260
dmi.product.version: V1.01
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[James Hunt (jamesodhunt)]

Interesting messages:

(WW) SynPS/2 Synaptics TouchPad can't grab event device, errno=16
(EE) intel(0): Couldn't create pixmap for fbcon

[James Hunt (jamesodhunt)]

Re-installed and have exactly the same issue again.

[James Hunt (jamesodhunt)]

This time, I installed, rebooted, logged in and pressed ALT+S and typed "term". The unity menu popped up and then the cursor hung.

[James Hunt (jamesodhunt)]

Further info - I left the system for a while and came back to it. The cursor was still frozen, but behind the unity menu was the screensaver / locker. I entered my password which removed the locker window. What's interesting though is that as this happened the frozen cursor changed from a pointer to a "busy cursor" (spinning disk) and then back to a pointer. It's still unmovable though.

[Bryce Harrington (bryce)]

Sounds like it's not a video issue but rather the input driver. The -synaptics task should be sufficient.

Did you try plugging in an external usb mouse? If it is just the synaptics driver, then the usb mouse should work fine.

Does the issue occur *only* under the conditions you describe? (Screensaver on, then unplug, then unlock) Your comment #4 is a bit unclear if that's restating the same condition or a different one that has the same fault.

You didn't mention if this was the first time ubuntu has been on that laptop, or if you had been running an earlier Ubuntu on it. I'd like to know if this is a regression from natty. If so, it might be fruitful to try installing and booting the oneiric kernel and see if the issue occurs with that.

The log messages you mention in comment #2 may or may not be relevant; try doing a tail -f /var/log/Xorg.0.log in a window and then reproduce the bug and see if those messages correlate to when the fault triggers.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.