Comment 1 for bug 1188824

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.