installation of autopilot-touch changes ownership of /dev/uinput to root:root

[Jean-Baptiste Lallement]

After installation of a touch device (in my case a mako with image 20130801), mode of /dev/uinput is set to:
# ls -l /dev/uinput
crw-rw---- 1 system bluetooth 10, 223 Aug 1 14:28 /dev/uinput

After installation of the package autopilot-touch, it changes to:
# ls -l /dev/uinput
crw-rw---- 1 root root 10, 223 Aug 1 14:28 /dev/uinput

After a reboot of the device, permissions are restored to their initial value (system/bluetooth)

This makes the default user 'phablet' unable to use the device /dev/uinput immédiately after installation of the package without rebooting or restoring the mode of the device first.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: autopilot-touch (not installed)
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Thu Aug 1 16:32:39 2013
InstallationDate: Installed on 2012-10-25 (279 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
SourcePackage: autopilot
UpgradeStatus: Upgraded to saucy on 2012-12-02 (242 days ago)

[Andy Doan (doanac)]

To add a note:

# autopilot from main
python-autopilot - changes to:
  crw-rw---- 1 root autopilot (differs from lp bug)

# autopilot from ppa
  crw-rw---- 1 root root 10, 223 Aug 1 16:11 /dev/uinput

Since the original permissions on /dev/uinput seem okay for phablet (its a member of bluetooth), do we really need the 61-autopilot-uinput.rules file in our packaging?

[Andy Doan (doanac)]

removing debian/61-autopilot-uinput.rules and its reference from debian/python-autopilot.install fixes it on touch. However, I suspect that will break things on the desktop. Not sure the proper way to do the packaging for such a fix?

[Thomi Richards (thomir-deactivatedaccount)]

We need this to work on desktop and it's currently broken, so I suspect this is a bug for both Desktop *and* Touch devices.

[Andy Doan (doanac)]

NOTE: Evidently this is being fixed in today's 2nd touch build (20130826.1). We should check after it lands if this bug can be closed.

[Andy Doan (doanac)]

I can confirm this is fixed

[Thomi Richards (thomir-deactivatedaccount)]

Closing this bug since, as per Andy's comment. This is now fixed:

crw-rw---- 1 root autopilot 10, 223 Jan 14 2000 /dev/uinput