Touchpad configuration reset after suspend/resume on MacBookAir4,2

Bug #954600 reported by Reuben Thomas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On my Macbook Air 4,2 I have set it in System Settings to disable mouse clicks with touchpad. This setting works fine, but after suspend and resume, the touchpad once again sends mouse clicks, and I have to toggle the setting back on then off again to set the desired (no clicks from touchpad) behaviour.

I have no idea which package is really responsible, but the kernel seems the logical place to start; if I can supply any more information, don't hesitate to ask.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-18-generic 3.2.0-18.29
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: Cirrus Analog [Cirrus Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rrt 6828 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xa0600000 irq 47'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10134206,106b5b00,00100302 HDA:80862805,80860101,00100000'
   Controls : 30
   Simple ctrls : 10
Date: Wed Mar 14 00:03:41 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Apple Inc. MacBookAir4,2
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-18-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-18-generic N/A
 linux-backports-modules-3.2.0-18-generic N/A
 linux-firmware 1.71
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-02-12 (30 days ago)
dmi.bios.date: 06/30/2011
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA41.88Z.0077.B00.1106300929
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-742912EFDBEE19B3
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir4,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-742912EFDBEE19B3
dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
dmi.product.name: MacBookAir4,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Reuben Thomas (rrt) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Seth Forshee (sforshee) wrote :

Odd, I don't see this on the 4,1, which is mostly identical to your machine.

At any rate, this doesn't sound like a kernel problem. Pushing this up the stack to xorg.

affects: linux (Ubuntu) → xserver-xorg-input-synaptics (Ubuntu)
Bryce Harrington (bryce)
summary: - Touchpad configuration reset after suspend/resume
+ Touchpad configuration reset after suspend/resume on MacBookAir4,2
Revision history for this message
Bryce Harrington (bryce) wrote :

Betting this has the same root cause as bug 968845

Revision history for this message
Reuben Thomas (rrt) wrote :

I've tried the workaround given at bug #968845; indeed, I've had the usbhid and bcm5974 modules listed in SUSPEND_MODULES ever since I first installed Ubuntu. I can therefore say that that workaround does not fix the bug I've reported. However, perhaps the workaround actually CAUSES the bug I'm experiencing, because when I suspend and resume my machine, the touchpad is reset? Is there some way I can get my configuration reapplied when the bcm5974 module is reloaded on resume?

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.