8bc91ac80f
This partially reverts commit de5cd71. Problem with that commit is, that it practically renders the "session-auth-*" signals from vnc session useless. That's because gtk-vnc currently emits "vnc-error" before each "vnc-auth-*" signal and the error callback in virt-viewer-app.c calls virt_viewer_app_disconnected(), which in turn closes the session. As a consequence, virt-viewer never retries authentication with vnc, it simply exits. Since the last commit, vnc, similarly to spice, emits "session-disconnected" with the appropriate error message. Thus there's no need to maintain separate "session-error" signal for now. With vnc, this error message is shown to the user in a dialog, if the disconnect happened during the init phase. "session-auth-*" callbacks create their own dialogs, so initialized must be set to TRUE to avoid having a dialog displayed twice. Related: https://bugzilla.redhat.com/show_bug.cgi?id=1911224 Signed-off-by: Jakub Janků <jjanku@redhat.com>
Virt Viewer
Virt Viewer provides a graphical viewer for the guest OS display. At this time is supports guest OS using the VNC or SPICE protocols. Further protocols may be supported in the future as user demand dictates. The viewer can connect directly to both local and remotely hosted guest OS, optionally using SSL/TLS encryption.
Virt Viewer is the GTK3 application. Virt Viewer 3.0 was the last release that supported GTK2.
Virt Viewer uses the GTK-VNC (>= 0.4.0) widget to provide a display of the VNC protocol, which is available from
https://wiki.gnome.org/Projects/gtk-vnc
Virt Viewer uses the SPICE-GTK (>= 0.35) widget to provide a display of the SPICE protocol, which is available from:
https://www.spice-space.org/download.html
Use of either SPICE-GTK or GTK-VNC can be disabled at time
of configure, with --without-gtk-vnc or --without-spice-gtk
respectively.
Virt Viewer uses libvirt to lookup information about the guest OS display. This is available from
Bug reports / support questions should be submitted to
https://gitlab.com/virt-viewer/virt-viewer/-/issues
Code contributions should be submitted as merge requests to