Bug 1004775

Summary: virtual-manager fails to connect to qemu:///system due to polkit error
Product: [Fedora] Fedora Reporter: Dennis Jacobfeuerborn <dennisml>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: berrange, crobinso, hbrock, jforbes, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-05 14:53:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dennis Jacobfeuerborn 2013-09-05 13:03:24 UTC
When i start virt-manager and try to collect to localhost I get this:

=======================
Unable to connect to libvirt.

authentication failed: polkit: polkit\56retains_authorization_after_challenge=1
Authorization requires authentication but no agent is available.

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1002, in _open_thread
    self.vmm = self._try_open()
  File "/usr/share/virt-manager/virtManager/connection.py", line 984, in _try_open
    flags)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 102, in openAuth
    if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: authentication failed: polkit: polkit\56retains_authorization_after_challenge=1
Authorization requires authentication but no agent is available.
=======================

Using virsh on the command line seems to work fine.

Comment 1 Dennis Jacobfeuerborn 2013-09-05 13:22:38 UTC
I just checked on the machine itself and there it works. The issue only seems to occur when the virt-manager display is exported to another machine (i.e. "ssh -X" to the machine and then starting virt-manager).

Comment 2 Cole Robinson 2013-09-05 14:53:41 UTC

*** This bug has been marked as a duplicate of bug 873799 ***