Bug 1377214 - Virt-viewer can't connect to guest graphic with non-root user and vnc listening on unix socket
Summary: Virt-viewer can't connect to guest graphic with non-root user and vnc listeni...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-viewer
Version: 6.9
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Grunt
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1377100
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 08:41 UTC by Xiaodai Wang
Modified: 2017-03-21 09:20 UTC (History)
11 users (show)

Fixed In Version: virt-viewer-2.0-16.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1377100
Environment:
Last Closed: 2017-03-21 09:20:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
virt-viewer debug log (2.84 KB, text/plain)
2016-10-08 03:21 UTC, Xiaodai Wang 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0587 0 normal SHIPPED_LIVE libgovirt, rest, spice-gtk, and virt-viewer bug fix and enhancement update 2017-03-21 12:24:45 UTC

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
Note You need to log in before you can comment on or make changes to this bug.