[Bug 1923363] Re: Users are not added to various groups (dialout, video, etc.)

[Dave Jones]

Per vorlon's comments on the merge request, I've closed the merge and
will re-submit an alternative method using udev rules instead of group
membership. Adding ubuntu-settings for the udev rules, and cloud-init as
we presumably want to remove membership in those groups from server
instances too.

** Tags added: foundations-todo

** Summary changed:

- Users are not added to various groups (dialout, video, etc.)
+ Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

** Also affects: ubuntu-settings (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Impish)
       Status: New => Won't Fix

** Changed in: cloud-init (Ubuntu Jammy)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Kinetic)
       Status: New => Won't Fix

** Changed in: cloud-init (Ubuntu Lunar)
       Status: New => Won't Fix

** Changed in: cloud-init (Ubuntu Mantic)
       Status: New => Confirmed

** Changed in: ubiquity (Ubuntu Impish)
       Status: Won't Fix => Invalid

** Changed in: ubiquity (Ubuntu Jammy)
       Status: Confirmed => Invalid

** Changed in: ubiquity (Ubuntu Kinetic)
       Status: Won't Fix => Invalid

** Changed in: ubiquity (Ubuntu Lunar)
       Status: Won't Fix => Invalid

** Changed in: ubiquity (Ubuntu Mantic)
       Status: Confirmed => Invalid

** Changed in: ubuntu-settings (Ubuntu Impish)
       Status: New => Won't Fix

** Changed in: ubuntu-settings (Ubuntu Jammy)
       Status: New => Confirmed

** Changed in: ubuntu-settings (Ubuntu Kinetic)
       Status: New => Won't Fix

** Changed in: ubuntu-settings (Ubuntu Lunar)
       Status: New => Won't Fix

** Changed in: ubuntu-settings (Ubuntu Mantic)
       Status: New => Confirmed

** Changed in: user-setup (Ubuntu Impish)
       Status: Won't Fix => Invalid

** Changed in: user-setup (Ubuntu Jammy)
       Status: Confirmed => Invalid

** Changed in: user-setup (Ubuntu Kinetic)
       Status: Won't Fix => Invalid

** Changed in: user-setup (Ubuntu Lunar)
       Status: Won't Fix => Invalid

** Changed in: user-setup (Ubuntu Mantic)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1923363

Title:
  Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

Status in cloud-init package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in user-setup package in Ubuntu:
  Invalid
Status in cloud-init source package in Impish:
  Won't Fix
Status in ubiquity source package in Impish:
  Invalid
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in user-setup source package in Impish:
  Invalid
Status in cloud-init source package in Jammy:
  Confirmed
Status in ubiquity source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  Confirmed
Status in user-setup source package in Jammy:
  Invalid
Status in cloud-init source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  Won't Fix
Status in user-setup source package in Kinetic:
  Invalid
Status in cloud-init source package in Lunar:
  Won't Fix
Status in ubiquity source package in Lunar:
  Invalid
Status in ubuntu-settings source package in Lunar:
  Won't Fix
Status in user-setup source package in Lunar:
  Invalid
Status in cloud-init source package in Mantic:
  Confirmed
Status in ubiquity source package in Mantic:
  Invalid
Status in ubuntu-settings source package in Mantic:
  Confirmed
Status in user-setup source package in Mantic:
  Invalid

Bug description:
  We're attempting to make the GPIO system on the Raspberry Pi images
  work "out of the box" on the new image. By default, GPIO kernel
  devices are made available to members of the "dialout" group which the
  initial user is added to by default on our server images. However,
  we've noticed that this isn't the case on the desktop images.

  The regression potential is minimal; the group already exists and
  we're simply adding the freshly created user to a new group and not
  removing any existing memberships. The group in question ("dialout")
  is also rarely used these days except for providing access to serial
  consoles, and as mentioned above is already a default membership on
  the server images. The change has been tested on the desktop image
  successfully.

  A test build of the updated image will be made under
  https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
  attach a debdiff shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+subscriptions