libvirt-qemu should be a system account

Bug #1674765 reported by Joseph Borg on 2017-03-21
This bug affects 6 people
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)

Bug Description

When installing libvirt, the user 'libvirt-qemu' is created, but not set as a system account so it appears on the login screen. Current workaround is:

echo -e "[User]\nSystemAccount=true" > /var/lib/AccountsService/users/libvirt-qemu

This is on 16.04.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libvirt (Ubuntu):
status: New → Confirmed
GrzesiekC (grzesiekc) wrote :

Hi all,

There is another solution here (Apr 14 at 11:11):

For whatever reason the system user "libvirt-gemu" is created with the uid 64055 (at least in Ubuntu 16.04.2).

This is how 16.04.2 creates it:

libvirt-qemu:x:64055:130:Libvirt Qemu,,,:/var/lib/libvirt:/bin/false
libvirt-dnsmasq:x:121:129:Libvirt Dnsmasq,,,:/var/lib/libvirt/dnsmasq:/bin/false

And this is how it should be:

libvirt-qemu:x:125:130:Libvirt Qemu,,,:/var/lib/libvirt:/bin/false
libvirt-dnsmasq:x:121:129:Libvirt Dnsmasq,,,:/var/lib/libvirt/dnsmasq:/bin/false

To correct this simply change the uid of "libvirt-qemu" and it's belonging files. "Libvirt Qemu" will then disappear from the login!

Read e.g. nixCraft - How to Change a USER and GROUP ID on Linux For All Owned Files to know how to do this.

Which one is the "proper" one ?

Lucas Levrel (llev) wrote :

This is not a duplicate of bug #857651 . This one depends on that one, but it's not the same. This bug wouldn't exist if the UID of libvirt-qemu was <1000 (or <500, maybe that depends on /etc/login.defs).

Hi Lucas, the problem is multi faceted.
Whenever possible it has to be a defined number to e.g. avoid permission issues on migration.
It was requested in [1] to ensure this across Debian/Ubuntu releases and works fine for that.

But in there you will not only see libvirt-qemu, you will see plenty of accounts, all of them "system" accounts but not with uid <1000.
All of the accounts you see there are affected by the same issue, and unless that there is a major overhaul for pre-allocated UIDs to get them in the range of <1000.
In hindsight one might ask to get all those to be added <99 in the master pwd file, but TBH that almost never happens as the risk for colissions is probably too high.

Then in turn this was working in the past and it was working on other Desktop environments.
See the discussions in bug 1667113 and bug 857651.

Let me try to unify the bugs, ping them and ask the Desktop Team for a pre an answer if this could at least be resolved towards 20.04.


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.