Bug 1377214

Summary: Virt-viewer can't connect to guest graphic with non-root user and vnc listening on unix socket
Product: Red Hat Enterprise Linux 6 Reporter: Xiaodai Wang <xiaodwan>
Component: virt-viewerAssignee: Pavel Grunt <pgrunt>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9CC: cfergeau, dblechte, fjin, juzhou, mzhan, pgrunt, rbalakri, tzheng, virt-bugs, virt-viewer-maint, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: virt-viewer-2.0-16.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1377100 Environment:
Last Closed: 2017-03-21 09:20:09 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:
Bug Depends On: 1377100    
Bug Blocks:    
Attachments:
Description Flags
virt-viewer debug log none

Comment 3 Pavel Grunt 2016-10-05 07:13:06 UTC
It is a permission "problem", not a bug. The only issue is that user is not informed through the gui.

Please attach the debug log (it would be different than the one from the bug 1377100 due to dependencies)

Thanks

Comment 4 Xiaodai Wang 2016-10-08 03:21:06 UTC
Created attachment 1208285 [details]
virt-viewer debug log

Comment 7 Xiaodai Wang 2016-12-07 06:33:24 UTC
I verified it with virt-viewer-2.0-17.el6.x86_64.

Configure a vnc unix guest, then connect to it by normal user.

$ virt-viewer -c qemu:///system testvnc

And error dialog "Failed to connect: Connecting to unix socket failed: Permission denied" pops.

So move the bug from ON_QA to VERIFIED.

Comment 9 errata-xmlrpc 2017-03-21 09:20:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0587.html