installation of autopilot-touch changes ownership of /dev/uinput to root:root
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
Fix Released
|
Undecided
|
Unassigned | ||
autopilot (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
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)
ProcVersionSign
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)
tags: | added: qa-touch |
Changed in autopilot (Ubuntu): | |
status: | New → Confirmed |
Changed in autopilot: | |
status: | New → Confirmed |
Changed in autopilot (Ubuntu): | |
importance: | Undecided → High |
tags: | added: rls-s-incoming |
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?