Hi Ayslinn,
thanks for your report.
The users are actually only tried to be removed as there might be e.g. running
processes or files of them. But it is not an issue if they stay behind, so
normally this would be on install -> purge.
Removing libvirt-daemon-system (4.0.0-1ubuntu8) ...
Warning: Stopping virtlogd.service, but it can still be activated by:
virtlogd.socket
Removing libvirt-daemon dnsmasq configuration
(Reading database ... 56452 files and directories currently installed.)
Purging configuration files for libvirt-daemon-system (4.0.0-1ubuntu8) ...
userdel: user libvirt-dnsmasq is currently used by process 438
/usr/sbin/deluser: `/usr/sbin/userdel libvirt-dnsmasq' returned error code 8.
Exiting.
userdel: user libvirt-dnsmasq is currently used by process 438
/usr/sbin/deluser: `/usr/sbin/userdel libvirt-dnsmasq' returned error code 8.
Exiting.
dpkg: warning: while removing libvirt-daemon-system, directory
'/var/lib/libvirt/qemu/channel/target' not empty so not removed
dpkg: warning: while removing libvirt-daemon-system, directory
'/etc/libvirt/qemu' not empty so not removed
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10) ...
So yeah users are not removed but that is ok - intentional to not break other
uses, and better to keep it around.
So I wonder why it behaves differently for you than for me as shown above.
>From your log:
Purging configuration files for libvirt-daemon-system (4.0.0-1ubuntu8) ...
/usr/sbin/delgroup: `libvirt-dnsmasq' still has `libvirtd' as their primary
group!
/usr/sbin/delgroup: `libvirt-dnsmasq' still has `libvirt' as their primary
group!
userdel: group libvirt-dnsmasq not removed because it is not the primary group
of user libvirt-dnsmasq.
dpkg: error processing package libvirt-daemon-system (--purge):
So this is either a red-herring and the error in your case comes AFTER
these messages about the user or something is different in your setup
than in "the normal one".
I just checked the postrm script, and it really has || bin/true on all these
calls for the reasons outlined above.
So those calls should never be the reason that this fails.
To check what goes on in your case you could (if you want) try to debug it.
First of all is the issue reproducible if you do.
$ apt install libvirt-daemon-system
$ apt remove --purge libvirt-daemon-system
If the above reproduces the error then please do
$ apt install libvirt-daemon-system
# edit /var/lib/dpkg/info/libvirt-daemon-system.postrm
# change set -e to set -ex
$ apt remove --purge libvirt-daemon-system
The latter should then be far more verbose on the console, please report
back the full output of that terminal then so that we can think together
what it could be.
Until that data is available there is not much more I can do atm, so
setting to incomplete for now.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769511
Title:
package libvirt-daemon-system (not installed) failed to
install/upgrade: installed libvirt-daemon-system package post-removal
script subprocess returned error exit status 128
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1769511/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
