Created attachment 453263 [details] Logfile produced by virt-manager I have not installed/used virtualization on this machine previously. 1. Updated from F13 to F14 2. Ran "yum install @virtualization" 3. Ran "service libvirtd start" 4. Tried to run virt-manager but got the same traceback as in comment 3. If I try to run virt-manager as root it fails and I get the following output: /usr/lib/python2.7/site-packages/dbus/types.py:6: PendingDeprecationWarning: The CObject type is marked Pending Deprecation in Python 2.7. Please use capsule objects instead. from _dbus_bindings import ObjectPath, ByteArray, Signature, Byte,\ ** GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL) Aborted (core dumped) Description of problem: When I try to run virt-manager connecting to the daemon fails: """ authentication failed Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 983, in _try_open None], flags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 111, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: authentication failed """ Version-Release number of selected component (if applicable): 0.8.5 How reproducible: Always Steps to Reproduce: 1. yum install @virtualization 2. service libvirtd start 3. virt-manager Actual results: Error dialog, cannot connect to daemon Expected results: No error Additional info: Installed after upgrading to F14 /var/log/messages contains: "Oct 13 21:32:15 beryllium libvirtd: 21:32:15.334: error : remoteDispatchAuthPolkit:3843 : Policy kit denied action org.libvirt.unix.manage from pid 3084, uid 500, result: 512"
I ran into this bug too... but noticed that if I run virt-manager as root, it works fine. In the past, running virt-manager as a user would prompt for the root password... but it no longer is... which I assume is causing this error.
Hmm, the original bug report says that they are running virt-manager as root... but in my cause, I can run it as root just fine... and it is only when run as a user do I get the error reported. Version of virt-manager: virt-manager-0.8.5-1.fc14.noarch
This problem has cleared itself up for me after numerous packages updates leading to the final release of Fedora 14. I couldn't tell you what fixed it... just that I no longer am experiencing the problem.
If I login to a Gnome graphical desktop then do an 'su' to root, and run virt-manager I get the issue, If I run 'su -' I don't get it.
The su vs. su - issue is a separate bug that doesn't appear to be virt-manager specific. i've filed that against gconf: https://bugzilla.redhat.com/show_bug.cgi?id=681390 the other issues have already been reported. duping *** This bug has been marked as a duplicate of bug 579579 ***