[Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

Mauricio Faria de Oliveira mauricfo at linux.vnet.ibm.com
Fri Feb 24 13:21:07 UTC 2017


Thanks for handling this.

> But the more that are affected the more I think then general solution
in lightdm would be the right thing to do.

Yes, that's my interpretation too -- and it was my impression from the
beginning, with your report/analysis, as I couldn't find anything we
were doing wrong with the useradd of a system account, and specially due
to this documentation statement (comment #7):

> [...] filters out those with UID values which are below a threshold
point to screen out system users [...]

Which does not cover the possible conditions for a system user (man 8

       -r, --system
           Create a system account.

           System users will be created with no aging information in /etc/shadow, and their
           numeric identifiers are chosen in the SYS_UID_MIN-SYS_UID_MAX range, defined in
           /etc/login.defs, instead of UID_MIN-UID_MAX (and their GID counterparts for the
           creation of groups).

           Note that useradd will not create a home directory for such an user, regardless of the
           default setting in /etc/login.defs (CREATE_HOME). You have to specify the -m options
           if you want a home directory for a system account to be created.

You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ceph in Ubuntu.

  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
Status in base-passwd package in Ubuntu:
Status in ceph package in Ubuntu:
Status in ifmail package in Ubuntu:
Status in libvirt package in Ubuntu:
Status in lightdm package in Ubuntu:
Status in netqmail package in Ubuntu:

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the Ubuntu-openstack-bugs mailing list