SRU Justification
=================
[Impact]
Without this fix, new multitouch devices connected to a computer after the user has logged in will not be recognized. They will continue to work as normal pointing devices, but they will fail to work for gesture handling.
[Test Case]
Obtain a detachable multitouch device, such as an Apple Magic Trackpad. Leave it disconnected at first. Log in to Unity. Connect the device. Attempt to perform a gesture, such as a four touch tap to open the dash. The gesture should work.
[Regression Potential]
Small. The code change is fairly trivial and should not cause any regression. Any regression that may be seen would involve devices not generating gestures due to mismatched gesture subscriptions. If gestures continue to work for all devices, then there is likely no regression.
Original Bug Report
===================
If I connect my magic touchpad after Unity has launched - in this case, by clicking on it to wake it up and re-pair it with the desktop - then it works fine as a touchpad but Unity fails to receive multitouch (three-finger move, four finger swipe/tap) gestures. Restarting Unity gets those gestures back.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libutouch-geis1 2.2.9-0ubuntu3
ProcVersionSignature: Ubuntu 3.4.0-3.8-generic 3.4.0
Uname: Linux 3.4.0-3-generic x86_64
ApportVersion: 2.1.1-0ubuntu1
Architecture: amd64
CurrentDmesg:
Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
dmesg: write failed: Broken pipe
Date: Wed Jun 6 10:25:50 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120321)
LsInput: Error: command ['gksu', '-D', 'Apport', '--', 'env', '-u', 'LANGUAGE', 'LC_MESSAGES=C', 'lsinput'] failed with exit code 127:
MachineType: Intel Corporation 2012 Client Platform
MtDevices: Apple Wireless Trackpad: /dev/input/event12
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.4.0-3-generic root=UUID=aec9f3df-6681-49ab-8357-eaa169fccc7f ro rootflags=subvol=@ quiet splash vt.handoff=7
SourcePackage: utouch-geis
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ACRVMBY1.86C.0078.P00.1201161002
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Emerald Lake 2
dmi.board.vendor: Intel Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0078.P00.1201161002:bd01/16/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnEmeraldLake2:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
dmi.product.name: 2012 Client Platform
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Intel Corporation
I confirm this. I think it always had this problem.
Thanks for the report.