1

I didn't create this user - I think it was added by installing the "Virtual Machine manager" (virt-manager) on Debian10/KDE.

grep -E 'libvirt|qemu' /etc/passwd returns libvirt-qemu:x:6xxxx: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. I don't have a file /var/lib/AccountsService/users/libvirt-qemu like described in a solution to the 2017 question here and could not find a bug report if it's due to a bug in accountsservice (why does the bug occur / why hasn't it been fixed since?).

Why is this user created and how to remove it but still be able to use virt-manager? 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.

14
  • 2
    System users like that are generally created so that daemons can run without root privs, or drop root privs as soon as possible. IIRC, user libvirt-qemu is created by the libvirt-daemon-system package, not virt-manager. It probably wasn't hidden by default because 1. every display manager has its own, different way of hiding users and 2. the package devs probably didn't think about it because they've done the the sane, secure thing on their systems and disabled the "show user list" anti-feature on their display manager (showing a user list harms security because it reveals usernames).
    – cas
    Aug 9 at 3:47
  • That's helpful. I guess in that case there should be some API or cross-DPM config file. (And it would still be a bug.) Where can one disable showing a user list in KDE? It only shows on the login screen (no other system-users are shown there) but not in the User Manager
    – mYnDstrEAm
    Aug 9 at 9:00
  • 1
    according to apt-cache show sddm, the sddm package doesn't list accountsservice in a Depends:, Recommends: or even Suggests: line. I don't think sddm uses it. Same for xdm, wdm, and lxdm. By way of contrast, gdm3 depends on it (so uses it and requires it), and lightdm Suggests it (uses it if it's installed, but doesn't require it).
    – cas
    Aug 10 at 14:00
  • 1
    The issue should have been created on Debian, which is the one doing the integration between unrelated components, and which chose the UID. libvirtd doesn't have to care about a login screen, nor a login screen has to care about each and every user installed not as it would expect. It's about harmonious integration with UID 64055 (no need to hide it, all debian installations default to 64055). Here is the likely bug fix having created this arguably bug: bugs.debian.org/cgi-bin/bugreport.cgi?bug=844339 . A guest migration in a cluster working fine is better than a gui minor issue.
    – A.B
    Aug 26 at 12:45
  • 1
    The fixed but isn't a display bug. The fixed bug is a bug about a live VM migration on a cluster of hypervisors
    – A.B
    Aug 26 at 15:02
1

It seems to be due to a bug in accountsservice in some cases. I have created a bug report here using info provided by users cas and A.B. who made some helpful comments above. Other than that it seems to be caused by the UID being too large and I have created another bug report here.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.