[Pkg-libvirt-maintainers] Bug#993047: A libvirt-qemu user is added and shown on the login screen because the UID is too high

mYnDstrEAm mYnDstrEAm at protonmail.ch
Thu Aug 26 22:01:07 BST 2021


Package: libvirt
Version: 5.0.0

I didn't create this user - I think it was added by installing the "Virtual Machine manager" (virt-manager) on Debian10/KDE, or more specifically by libvirt-daemon-system.

`grep -E 'libvirt|qemu' /etc/passwd` returns `libvirt-qemu:x:64055:1xx:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin`
KDE's User Manager doesn't show the account but it's displayed on the login screen on the left of the actual user account (not when locking the screen but at least after booting).

This useraccount shouldn't be displayed as a normal user if adding it is indeed needed/useful.
If the solution is to not remove the user but to hide it by creating the /users/libvirt-qemu file why isn't that done when the user is set up already? If the user is necessary I'd find it strange that iirc it was only added after installing virt-manager but not after installing and using aqemu.

I asked about it here where users cas and A.B. made some helpful comments. A.B. suggested that "libvirt-qemu is a system account but with a specific UID not in the default system range ( < 500 or something like this): `grep LIBVIRT_QEMU_UID /var/lib/dpkg/info/libvirt`*" (it's over 60000). Changing the UID or creating that config-file containing `SystemAccount=true` upon installation seem to be two ways of solving this issue.

Per https://github.com/sddm/sddm/issues/816 it really seems to be a bug of virt-manager. I don't know if this has been fixed in newer versions. If the solution really is just changing the UID there may be an additional issue of 500 being too low. It should probably check which UIDs within that range are still available and then assign one of these. It seems like running `usermod -u 345 libvirt-qemu` would solve the issue for those affected, right?

Per https://github.com/virt-manager/virt-manager/issues/293 the problem is the hard-coded UID here: https://salsa.debian.org/libvirt-team/libvirt/-/blob/debian/buster/debian/libvirt-daemon-system.config

It would be great if people would set up a proper issue-tracking system for Debian (one that's modern, somewhat convenient to use, doesn't look outdated by decades and is Web-based).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-maintainers/attachments/20210826/28da531a/attachment.htm>


More information about the Pkg-libvirt-maintainers mailing list