This isn't really sufficient...
If you've *ever* started virt-manager without libvirt running then it
will have created the qemu:///session connection. This means that on
future restarts the connection list won't be empty and it won't scan for
the qemu:///system socket being available.
The only workaround for this is to start the libvirtd-bin service, start
virt-manager, delete all connections from virt-manager, close virt-
manager then restart virt-manager. That's a bit much to ask.
** Changed in: virt-manager (Ubuntu)
Status: Invalid => New
--
virt-manager has a hard time connecting to root-owned libvirtd
https://bugs.launchpad.net/bugs/586115
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
