/dev/autopilot-uinput and udev rules files does not exist
Bug #1188824 reported by
Nicholas Skaggs
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
Fix Released
|
High
|
Francis Ginther |
Bug Description
Running saucy with autopilot 1.3.1 and recieved this error on boot:
[ 16.942650] systemd-udevd[647]: NAME="autopilot
Upon investigation it appears the udev rules and /dev/autopilot* is missing completely.
Changed in autopilot: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
After installing python-autopilot on a saucy box, I see: uinput uinput: No such file or directory
fginther@sandman:~$ ll /dev/autopilot-
ls: cannot access /dev/autopilot-
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.