Comment 4 for bug 198957

I understand that its not a library package, thats not the point.
The point is that in a default installation a user will always get this error message when trying to connect to the local machine (which is the default connection offered at startup). I would suggest that connecting to a remote libvirtd is not the first option most people would be trying.

Anyone trying to use Virtmanager for the first time, with default options, will always get this error and won't be able to do anything until libvirtd is running (which is contained in the libvirt-bin package, not installed by default). No one should have to look at that error message and work out for themselves what has to be done to get thing working when the default install of one small package could resolve the problem or perhaps a change to the user interface to make it explicit what the dependencies are.