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.
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.