Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1539148

Summary:	Fails to request x509 credentials from app when connecting to VNC server using TLS
Product:	Red Hat Enterprise Linux 7	Reporter:	amashah
Component:	gtk-vnc	Assignee:	Daniel Berrangé <berrange>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.4	CC:	fjin, jkoten, lottifran, mtessun, salmy, tpelka
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gtk-vnc-0.7.0-3.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 19:09:13 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 amashah 2018-01-26 19:10:50 UTC

Description of problem:
Two packages were updated on a RHEL 7.4 system:

  Updating   : gvnc-0.7.0-2.el7.x86_64
  Updating   : gtk-vnc2-0.7.0-2.el7.x86_64
  Cleanup    : gtk-vnc2-0.5.2-7.el7.x86_64
  Cleanup    : gvnc-0.5.2-7.el7.x86_64

When using virt-manager to connect to a remote VM, the console does not come up.  If the packages are downgraded back to 0.5.2-7, the VM console comes up.

This particular environment is connecting to a remote VM.

Version-Release number of selected component (if applicable):

0.7.0-2

How reproducible:
100%

Steps to Reproduce:
1. Update to packages to 0.7.0-2, try to bring up VM console, does not work
2. Revert packages to 0.5.2-7, VM console comes up
3. Try on another system, results are the same

Actual results:

VM Console disconnects.

Expected results:

VM Console should be displayed.

Additional info:

virt-manager debug output:
gtk-vnc2 0.5.2-7,

[Wed, 24 Jan 2018 12:52:55 virt-manager 3655] DEBUG (engine:401) window counter incremented to 2
[Wed, 24 Jan 2018 12:52:55 virt-manager 3655] DEBUG (console:718) Starting connect process for proto=vnc trans=tls connhost=**** connuser=root connport= gaddr=0.0.0.0 gport=5902 gtlsport=None gsocket=None
[Wed, 24 Jan 2018 12:52:56 virt-manager 3655] DEBUG (viewers:467) VNC connecting to host=**** port=5902
[Wed, 24 Jan 2018 12:52:56 virt-manager 3655] DEBUG (viewers:371) Got credential request <enum VNC_DISPLAY_CREDENTIAL_CLIENTNAME of type GtkVnc.DisplayCredential>
[Wed, 24 Jan 2018 12:52:56 virt-manager 3655] DEBUG (console:841) Viewer connected

gtk-vnc2 0.7.0-2
[Wed, 24 Jan 2018 12:49:10 virt-manager 2987] DEBUG (engine:401) window counter incremented to 2
[Wed, 24 Jan 2018 12:49:10 virt-manager 2987] DEBUG (console:718) Starting connect process for proto=vnc trans=tls connhost=**** connuser=root connport= gaddr=0.0.0.0 gport=5902 gtlsport=None gsocket=None
[Wed, 24 Jan 2018 12:49:10 virt-manager 2987] DEBUG (viewers:467) VNC connecting to host=**** port=5902
[Wed, 24 Jan 2018 12:49:11 virt-manager 2987] DEBUG (console:832) Viewer disconnected


The older package appears to have a credential request.

Comment 4 Daniel Berrangé 2018-01-31 11:32:24 UTC

Yep, this is a genuine bug in handling the CA certificate on the client side. When adding support for using the GNUTLS global CA trust DB, we accidentally broke the code that prompted the client for its TLS certs. This is now fixed upstream in

commit abc27748c6ca309ec3c39fb6c84426a459f56c74
Author: Daniel P. Berrangé <berrange>
Date:   Wed Jan 31 11:27:10 2018 +0000

    Explicitly track whether x509 creds have been set
    
    If we want to use the system trust DB, we can't rely on cred_x509_cacert
    field being non-NULL. We must explicitly record whether the client app
    has set the x509 credentials. We allow cacert to be missing if we are
    built against a new enough GNUTLS.
    
    Signed-off-by: Daniel P. Berrangé <berrange>

commit 8e14f8a00c486ac4a133fcd190526e73406d9cb6
Author: Daniel P. Berrangé <berrange>
Date:   Wed Jan 31 11:11:09 2018 +0000

    Add debug logs wrt credential gathering
    
    Signed-off-by: Daniel P. Berrangé <berrange>

commit df656c79467c2595b4a2cd35283c7f5d52adf336
Author: Daniel P. Berrangé <berrange>
Date:   Wed Jan 31 11:09:38 2018 +0000

    Don't short-circuit request for TLS credentials
    
    Although newer GNUTLS has a default system trust fallback for CA
    certificates, we must still request certificates from the client app. If
    we do not, then the VNC client will never be given the opportunity to
    provide custom certs to override the system trust database.
    
    Signed-off-by: Daniel P. Berrangé <berrange>


And we'll get these into RHEL builds.

As a temporary workaround, you might be able to get remote connections running again with:

  cd /etc/pki/ca-trust/source/anchors
  ln -s /etc/pki/CA/cacert.pem libvirt-ca.pem
  update-ca-trust

This will populate the global CA trust database with the libvirt specific CA you have. 

The one caveat is that this change applies to the *whole* system. ie any application using TLS will now see that libvirt CA. This shouldn't cause a problem, but you should be aware of it and ensure ability to issue certs from the libvirt CA is controlled.

Once we get this bug fixed you would be able to revert the workaround by just deleting that symlink and re-running update-ca-trust

Comment 8 Frastill 2018-02-23 22:39:35 UTC

I have the same problem with gtk-vnc2-0.7.1-6 and virt-viewer-6.0-3 on a Fedora 27 system.
If I try connecting to a remote virtual machine's vnc console with tls encryption I get no vnc display on the client side.

Same problem with virt-manager, whereas using another vnc client like remmina  and manually selecting client certificate, client key and CA certificate I get to the vm vnc console without any problems.

Populating the global ca trust with the libvirt CA didn't solve the problem.


[goo@darkgoo ~]$ virt-viewer --gtk-vnc-debug -c qemu+tls://hvmsrv03/system webspace

** (virt-viewer:32663): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-IEakupyfDw: Connection refused
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Init VncConnection=0x561bae82fba0
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Using X11 backend
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c XKB keyboard map name 'evdev+aliases(qwerty)'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Server vendor is 'Fedora Project'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Generic Event Extension'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SHAPE'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'MIT-SHM'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XInputExtension'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XTEST'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'BIG-REQUESTS'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SYNC'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XKEYBOARD'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XC-MISC'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFIXES'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RENDER'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RANDR'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XINERAMA'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Composite'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DAMAGE'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'MIT-SCREEN-SAVER'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DOUBLE-BUFFER'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RECORD'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DPMS'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Present'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DRI3'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'X-Resource'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XVideo'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XVideo-MotionCompensation'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFree86-VidModeExtension'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFree86-DGA'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DRI2'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'GLX'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SGI-GLX'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Using evdev keycode mapping
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c Grab sequence is now Control_L+Alt_L
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Open host=hvmsrv03.vms.ouverture.it port=5900
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Open coroutine starting
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Started background coroutine
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Resolving host hvmsrv03.vms.ouverture.it 5900
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Trying one socket
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Socket pending
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Finally connected
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Emit main context 13
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c Grab sequence is now Control_L+Alt_L
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c Connected to VNC server
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Protocol initialization
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable

(virt-viewer:32663): Gtk-WARNING **: Allocating size to VncDisplay 0x561bae82a210 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Server version: 3.8
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Sending full greeting
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Using version: 3.8
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Possible auth 19
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Emit main context 11
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Thinking about auth type 19
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Decided on auth type 19
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Waiting for auth type
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Choose auth 19
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Possible VeNCrypt sub-auth 260
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Emit main context 12
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Requested auth subtype 260
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Waiting for VeNCrypt auth subtype
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Choose auth 260
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Do TLS handshake
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c No CA certificate provided; trying the system trust store instead
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Using the system trust store and CRL
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c No client cert or key provided
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c No CA revocation list provided
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Handshake done
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Validating
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Certificate is valid.
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Checking chain 0
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Completed TLS setup, do subauth 260
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Completing auth
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Checking auth result
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Error: Unable to read from server
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Emit main context 16
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c VNC server error
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Success
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Doing final VNC cleanup
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Close VncConnection=0x561bae82fba0
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Emit main context 15
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c Disconnected from VNC server
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c Grab sequence is now Control_L+Alt_L
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Init VncConnection=0x561baef719e0
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Using X11 backend
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c XKB keyboard map name 'evdev+aliases(qwerty)'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Server vendor is 'Fedora Project'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Generic Event Extension'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SHAPE'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'MIT-SHM'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XInputExtension'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XTEST'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'BIG-REQUESTS'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SYNC'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XKEYBOARD'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XC-MISC'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFIXES'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RENDER'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RANDR'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XINERAMA'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Composite'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DAMAGE'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'MIT-SCREEN-SAVER'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DOUBLE-BUFFER'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RECORD'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DPMS'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Present'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DRI3'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'X-Resource'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XVideo'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XVideo-MotionCompensation'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFree86-VidModeExtension'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFree86-DGA'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DRI2'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'GLX'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SGI-GLX'
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplaykeymap.c Using evdev keycode mapping
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c Grab sequence is now Control_L+Alt_L
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c Display destroy, requesting that VNC connection close
(virt-viewer:32663): gtk-vnc-DEBUG: vncdisplay.c Releasing VNC widget
(virt-viewer:32663): gtk-vnc-DEBUG: vncconnection.c Finalize VncConnection=0x561baef719e0

Comment 9 Daniel Berrangé 2018-02-26 09:53:53 UTC

(In reply to Frastill from comment #8)
> I have the same problem with gtk-vnc2-0.7.1-6 and virt-viewer-6.0-3 on a
> Fedora 27 system.
> If I try connecting to a remote virtual machine's vnc console with tls
> encryption I get no vnc display on the client side.
> 
> Same problem with virt-manager, whereas using another vnc client like
> remmina  and manually selecting client certificate, client key and CA
> certificate I get to the vm vnc console without any problems.
> 
> Populating the global ca trust with the libvirt CA didn't solve the problem.

Presumably you have the VNC server setup to request client certificates too ?  The global CA trust only works for having the client validate the server cert. If the server is also requesting a  client cert, the workaround won't work. I suspect that's what happened, since the logs you provide show the client successfully locating the CA cert in the global trust.

Comment 10 Frastill 2018-03-17 19:40:20 UTC

Yes, I got libvirtd to request tls client verification (tls_no_verify_certificate = 0 in libvirtd.conf).

Again, building gtk-vnc from master and installing it over /usr/local solved the problem for me:

[goo@goowks ~]$ LD_LIBRARY_PATH=/usr/local/lib virt-viewer --debug --gtk-vnc-debug -c qemu+tls://hvmsrv03/system webplace

(virt-viewer:15096): virt-viewer-DEBUG: connecting ...
(virt-viewer:15096): virt-viewer-DEBUG: Opening connection to libvirt with URI qemu+tls://hvmsrv03/system
(virt-viewer:15096): virt-viewer-DEBUG: initial connect
(virt-viewer:15096): virt-viewer-DEBUG: notebook show status 0x5591ba5c2270
(virt-viewer:15096): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID changed to 924d3b75-666c-42d7-a429-7af3569eb054
(virt-viewer:15096): virt-viewer-DEBUG: notebook show status 0x5591ba5c2270
(virt-viewer:15096): virt-viewer-DEBUG: Guest webplace is running, determining display
(virt-viewer:15096): virt-viewer-DEBUG: Set connect info: (null),(null),-1,-1,(null),(null),(null),0
(virt-viewer:15096): virt-viewer-DEBUG: Guest webplace has a vnc display
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Init VncConnection=0x5591ba73d920
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Using X11 backend
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c XKB keyboard map name 'evdev+aliases(qwerty)'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Server vendor is 'Fedora Project'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Generic Event Extension'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SHAPE'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'MIT-SHM'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XInputExtension'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XTEST'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'BIG-REQUESTS'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SYNC'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XKEYBOARD'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XC-MISC'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFIXES'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RENDER'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RANDR'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XINERAMA'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Composite'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DAMAGE'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'MIT-SCREEN-SAVER'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DOUBLE-BUFFER'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'RECORD'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DPMS'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'Present'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DRI3'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'X-Resource'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XVideo'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XVideo-MotionCompensation'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFree86-VidModeExtension'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'XFree86-DGA'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'DRI2'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'GLX'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Found extension 'SGI-GLX'
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplaykeymap.c Using evdev keycode mapping
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Grab sequence is now Control_L+Alt_L
(virt-viewer:15096): virt-viewer-DEBUG: Guest graphics address is 0.0.0.0:5910
(virt-viewer:15096): virt-viewer-DEBUG: Guest graphics listen '0.0.0.0' is NULL or a wildcard, replacing with 'hvmsrv03'
(virt-viewer:15096): virt-viewer-DEBUG: Set connect info: hvmsrv03,hvmsrv03,5910,-1,tls,(null),(null),0
(virt-viewer:15096): virt-viewer-DEBUG: Error operation forbidden: read only access prevents virDomainOpenGraphicsFD
(virt-viewer:15096): virt-viewer-DEBUG: After open connection callback fd=-1
(virt-viewer:15096): virt-viewer-DEBUG: Opening direct TCP connection to display at hvmsrv03:5910:-1
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Open host=hvmsrv03 port=5910
(virt-viewer:15096): virt-viewer-DEBUG: notebook show status 0x5591ba5c2270
(virt-viewer:15096): virt-viewer-DEBUG: reconnect_poll: 0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Open coroutine starting
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Started background coroutine
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Resolving host hvmsrv03 5910
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Trying one socket
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Socket pending
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Finally connected
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Emit main context 13
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Grab sequence is now Control_L+Alt_L
(virt-viewer:15096): virt-viewer-DEBUG: notebook show status 0x5591ba5c2270
(virt-viewer:15096): virt-viewer-DEBUG: Insert display 0 0x5591ba4c6680
(virt-viewer:15096): virt-viewer-DEBUG: notebook show status 0x5591ba5c2270
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Connected to VNC server
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Protocol initialization
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Server version: 3.8
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Sending full greeting
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Using version: 3.8
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Possible auth 19
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Emit main context 11
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Thinking about auth type 19
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Decided on auth type 19
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Waiting for auth type
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Choose auth 19
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Checking if credentials are needed
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c No credentials required
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Possible VeNCrypt sub-auth 260
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Emit main context 12
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Requested auth subtype 260
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Waiting for VeNCrypt auth subtype
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Choose auth 260
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Checking if credentials are needed
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c No credentials required
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Do TLS handshake
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Checking if credentials are needed
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Want a TLS clientname
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Requesting missing credentials
(virt-viewer:15096): virt-viewer-DEBUG: Allocated 1024x741
(virt-viewer:15096): virt-viewer-DEBUG: Child allocate 1024x640

(virt-viewer:15096): Gtk-WARNING **: Allocating size to VncDisplay 0x5591ba72e250 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Emit main context 10
(virt-viewer:15096): virt-viewer-DEBUG: Got VNC credential request for 1 credential(s)
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Set credential 2 libvirt
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Searching for certs in /usr/local/etc/pki
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Searching for certs in /home/goo/.pki
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Failed to find certificate CA/cacrl.pem
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Waiting for missing credentials
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Got all credentials
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c No CA revocation list provided
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Handshake was blocking
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Handshake done
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Validating
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Certificate is valid.
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Checking chain 0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Completed TLS setup, do subauth 260
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Completing auth
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Checking auth result
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Success
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Initial desktop size 1024x768
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Pixel format BPP: 32,  Depth: 24, Byte order: 1234, True color: 1
             Mask  red: 255, green: 255, blue: 255
             Shift red:  16, green:   8, blue:   0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Display name 'QEMU (webplace)'
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Emit main context 14
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Using default colour depth 24 (32 bpp) (true color? 1)
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Set depth color to 24 (32 bpp)
(virt-viewer:15096): gtk-vnc-DEBUG: vnccairoframebuffer.c Surface 1024x768
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Set framebuffer 0x5591ba83ad10
(virt-viewer:15096): virt-viewer-DEBUG: desktop resize 1024x768
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Removed encoding -27
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Sending 14 encodings
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Requesting first framebuffer update
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 0
(virt-viewer:15096): virt-viewer-DEBUG: notebook show status 0x5591ba5c2270
(virt-viewer:15096): virt-viewer-DEBUG: Zoom level not changed, using: 100
(virt-viewer:15096): virt-viewer-DEBUG: notebook show display 0x5591ba5c2270
(virt-viewer:15096): gtk-vnc-DEBUG: vncdisplay.c Initialized VNC server
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Running main loop
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=-259 area (1024x768) at location 0,0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Audio encoding support
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=-258 area (1024x768) at location 0,0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Keyboard mode extended
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Re-requesting framebuffer update at 0,0 size 1024x768, incremental 0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=-257 area (1024x768) at location 1,0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Pointer mode absolute
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Re-requesting framebuffer update at 0,0 size 1024x768, incremental 0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=-261 area (1x1) at location 0,0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c LED state: 0

(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Emit main context 7
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Re-requesting framebuffer update at 0,0 size 1024x768, incremental 0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=5 area (1024x768) at location 0,0
(virt-viewer:15096): gtk-vnc-DEBUG: vncbaseframebuffer.c Mask local: 255 255 255
    remote: 255 255 255
    merged: 255 255 255
(virt-viewer:15096): gtk-vnc-DEBUG: vncbaseframebuffer.c Pixel shifts
   right:  16   8   0
    left:  16   8   0
(virt-viewer:15096): gtk-vnc-DEBUG: vncconnection.c Notify update area (1024x768) at location 0,0
(virt-viewer:15096): virt-viewer-DEBUG: Allocated 1024x768
(virt-viewer:15096): virt-viewer-DEBUG: Child allocate 1024x768

Comment 12 errata-xmlrpc 2018-04-10 19:09:13 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://access.redhat.com/errata/RHBA-2018:1045

Comment 13 Victor Toso 2018-12-19 16:15:52 UTC

*** Bug 1533805 has been marked as a duplicate of this bug. ***