libvirt-qemu user shows up on the new greeter as disabled

[ibrahimrahman]

It shouldn't be showing up at all. I'm using the .deb linked in Daniel Foré's Reddit post (3.3.1+r773+pkg61)

[danirabbit]

Can you do me a favor and paste the output of id -u libvert-qemu? I believe users with an ID below something like 1000 shouldn't show.

Also, is this issue new for the new greeter or are you experiencing it with the greeter shipped with 5.0 as well?

[ibrahimrahman]

❯ id -u libvirt-qemu
64055

This issue is specific to the new greeter. It did not show up on the older one (The user has always showed up in the User Accounts setting though. Not sure if it should or not).

[cassidyjames]

Looks like this is an upstream bug as well. More info at https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1667113

It sounds like we might be able to filter it out somehow?

[danirabbit]

From the discussion there it sounds like this is confirmed to be an issue either in lightdm or accountsservice and not an issue in a particular greeter implementation. I'd be inclined to mark this as "Out of scope" since a proper fix would occur there. But, I'm also interested in @tintou's opinion

[codygarver]

If you add libvirt-qemu to hidden-users in /etc/lightdm/users.conf does it fix the issue?

[ibrahimrahman]

No, the issue persists.

[ibrahimrahman]

printf "[User]\nSystemAccount=true\n" | sudo tee /var/lib/AccountsService/users/libvirt-qemu
sudo systemctl restart accounts-daemon.service 

This workaround mentioned here stops the user from showing up in both the greeter as well as the User Account settings. However, I'm uncertain if this counts as a proper fix or not

[endorama]

I found another reference of this issue in upstream Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1674765

Is confirmed happening on Ubuntu 18.04, which is probably why elementary users see it.

That Bug reference another one: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/857651, multiple fixes still to be released to see this one fixed completely.

[danirabbit]

Closing as "out of scope" since this has been confirmed to be an upstream issue