Hello,

This actually looks like a libvirt issue.

I can reproduce this with virt-manager and a usermode session,
apparently the daemon is not (always?) automatically started for the
user. (The system one is perfectly running).

Manually starting libvirtd seems to fix this.

I guess it should be reassigned properly.

Cheers,

Laurent Bigonville


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to