Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47205 - [filesystem] plugdev group request
Attached to Project:
Arch Linux
Opened by Kyle Keen (keenerd) - Saturday, 28 November 2015, 07:33 GMT
Last edited by Jan de Groot (JGC) - Sunday, 29 November 2015, 18:19 GMT
Opened by Kyle Keen (keenerd) - Saturday, 28 November 2015, 07:33 GMT
Last edited by Jan de Groot (JGC) - Sunday, 29 November 2015, 18:19 GMT
|
DetailsDescription:
For whatever reason, many pieces of engineering hardware use the "plugdev" group in their udev permissions configuration. On just my own laptop I have MCU programmers, software defined radios, and a USB oscilloscope that all set their access permissions to plugdev. The group name appears to have been created at Ubuntu, but has since then been accepted as the de facto standard for data acquisition and electronic tools. Several of my packages in [community] ship udev rules that use plugdev, and in the past I've included directions for creating the group locally. However adding plugdev to the default set of groups seems much cleaner. |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 29 November 2015, 18:19 GMT
Reason for closing: Won't implement
Sunday, 29 November 2015, 18:19 GMT
Reason for closing: Won't implement

Plugdev is an obsolete group to give members of that group full access to removable devices. Permissions on such devices are granted by logind using ACLs these days, so there's no need for plugdev. Any package shipping such rules should be considered buggy.

Agreed -- fix the rules. You can use TAG+="uaccess" to grant at-seat permissions to the device (implemented with ACLs).