/dev/autopilot-uinput and udev rules files does not exist

[Nicholas Skaggs]

Running saucy with autopilot 1.3.1 and recieved this error on boot:

[ 16.942650] systemd-udevd[647]: NAME="autopilot-uinput" ignored, kernel device nodes can not be renamed; please fix it in /lib/udev/rules.d/61-autopilot-uinput.rules:2

Upon investigation it appears the udev rules and /dev/autopilot* is missing completely.

[Francis Ginther (fginther)]

After installing python-autopilot on a saucy box, I see:
fginther@sandman:~$ ll /dev/autopilot-uinput
ls: cannot access /dev/autopilot-uinput: No such file or directory
fginther@sandman:~$ ll /dev/uinput
crw-rw---- 1 root autopilot 10, 223 Jun 7 15:55 /dev/uinput

So instead of creating the expected /dev/autopilot-uinput node as happens (or at least did happen) on raring, udev now appears to be just modifying the permissions on /dev/uinput. This isn't what we want, but it should still allow uinput based tests to run as autopilot will fallback to using /dev/uinput if /dev/autopilot-uinput is not writable.

[I Ahmad (iahmad)]

I was able to reproduce it on raring and have to manually use the command to fix the problem sudo chmod 666 /dev/autopilot-uinput. Ideally this should be handled during the python-autopilot pkg installation.

[Andy Doan (doanac)]

I think this is related to:

 https://bugs.launchpad.net/autopilot/+bug/1207386

Do we really need a /dev/autopilot-uinput node? or should we just remove the udev rule altogether on touch installs?

[Christopher Lee (veebers)]

Francis, is this still an issue or was it resolved with the release of the above bug (lp:1207386)?

[Francis Ginther (fginther)]

Chris, I can no longer reproduce this. Please close.