Bug 320650

Summary: Can't connect to a Xvnc server
Product: [Applications] krdc Reporter: Djuro Drljaca <djurodrljaca>
Component: VNCAssignee: Urs Wolfer <uwolfer>
Status: RESOLVED WORKSFORME    
Severity: grave CC: andrew.crouthamel, hardy.heroin, philipp.woelfel
Priority: NOR    
Version: 4.10.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Djuro Drljaca 2013-06-03 07:35:22 UTC 
When I try to connect to a Xvnc server it doesn't ask me for password and all I get is a blue background.

When I connect using vncviewer it works, but not when I use KRDC.

Here is the debug output when I run krdc from command line:
krdc(19087) MainWindow::loadAllPlugins: "# Plugin RDP found, however it's not activated, skipping..."
krdc(19087) MainWindow::loadAllPlugins: "### Plugin VNC found ###"
krdc(19087) MainWindow::loadAllPlugins: # Version: "1.0"
krdc(19087) MainWindow::loadAllPlugins: # Description: "Allows managing VNC sessions through KRDC"
krdc(19087) MainWindow::loadAllPlugins: # Author: "Urs Wolfer"
krdc(19087) MainWindow::loadAllPlugins: # Sorting: 20
krdc(19087) MainWindow::loadAllPlugins: "# Plugin Test found, however it's not activated, skipping..."
krdc(19087) RemoteDesktopsModel::RemoteDesktopsModel: Browsing for zeroconf hosts.
krdc(19087)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory! 
krdc(19087) MainWindow::updateActionStatus: -1
krdc(19087) MainWindow::tabChanged: 0
krdc(19087) MainWindow::updateActionStatus: 0
krdc(19087) MainWindow::newConnection: "Found plugin to handle url (vnc://192.168.2.1:2): VncView"
krdc(19087) HostPreferences::showDialogIfNeeded: Show config dialog again
krdc(19087) HostPreferences::showDialog: HostPreferences config dialog accepted
krdc(19087) MainWindow::tabChanged: -1
krdc(19087) MainWindow::updateActionStatus: -1
krdc(19087)/krdc (VNC backend) VncView::scaleResize: 1647 947
krdc(19087) MainWindow::tabChanged: 0
krdc(19087) MainWindow::updateActionStatus: 0
krdc(19087) MainWindow::tabChanged: 0
krdc(19087) MainWindow::updateActionStatus: 0
krdc(19087) MainWindow::statusChanged: -2
krdc(19087) MainWindow::statusChanged: -1
krdc(19087) MainWindow::statusChanged: 0
krdc(19087) main: ########## KRDC ready: 4875 ms ##########
krdc(19087)/krdc (VNC backend) VncClientThread::run: --------------------- trying init ---------------------
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "VNC server supports protocol version 3.8 (viewer 3.8)"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "We have 2 security types to read"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "0) Received security type 19"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Selecting security type 19 (0/2 in the list)"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "1) Received security type 2"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Selected Security Scheme 19"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "OpenSSL initialized."
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Got VeNCrypt version 0.2 from server."
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "We have 1 security types to read"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "0) Received security type 2"
krdc(19087)/krdc (VNC backend) VncClientThread::outputHandler: "Unknown VeNCrypt authentication scheme from VNC server: 2"
krdc(19087) MainWindow::disconnectHost:
krdc(19087)/krdc (VNC backend) VncView::startQuitting: about to quit
krdc(19087) MainWindow::statusChanged: -1
krdc(19087)/krdc (VNC backend) VncView::startQuitting: Quit VNC thread success: true
krdc(19087) MainWindow::statusChanged: -2
krdc(19087) MainWindow::tabChanged: -1
krdc(19087) MainWindow::updateActionStatus: -1
krdc(19087) MainWindow::tabChanged: 0
krdc(19087) MainWindow::updateActionStatus: 0

Reproducible: Always

Steps to Reproduce:
1. Connect to a Xvnc server
Actual Results:  
It doesn't connect. All I get is a blue background without any indication of an error.

Expected Results:  
It should connect.
Comment 1 Urs Wolfer 2013-06-03 08:11:22 UTC 
Did it work with an older version of KRDC with the same VNC setup?
Comment 2 Djuro Drljaca 2013-06-03 08:25:25 UTC 
I don't know. I just reinstalled my server (not it has opensuse 12.3 and I also have the same on my PC) an I didn't use VNC before (for some reason I am no longer able to connect to NX so I had to switch to VNC).

I think I locate the problem. It might be a problem in the libvncclient in function ReadVeNCryptSecurityType ( http://libvncserver.sourceforge.net/doc/html/tls__openssl_8c_source.html ) so it is probably upstream problem.

If you need some additional information about my system or maybe even to debug this over IRC then let me know.
Comment 3 Djuro Drljaca 2013-06-03 10:28:32 UTC 
I have exactly the same failure with remmina (vnc client) except that this one actually shows the error message :)
Comment 4 Urs Wolfer 2013-06-03 17:41:19 UTC 
Could you please also report this issue again libvncserver? Please post the task url here also. Thank you.

I will look into the issue why KRDC does not show any error message in the UI.
Comment 5 Djuro Drljaca 2013-06-03 18:12:27 UTC 
Here is the link to the libvncserver ticket: https://sourceforge.net/p/libvncserver/support-requests/8/
Comment 6 OpenSUSE User #314 2013-06-26 06:21:04 UTC 
Confirming this issue with openSUSE 12.3 (both client and server). Connecting using KRDC result in a blank screen, connecting using Remmina result in the error message "Unkown VeNCrypt authentication scheme from VNC server". Using vncviewer from the command line does work. Any further debug logs required? I suggest changing the status to confirmed.
Comment 7 Philipp Woelfel 2014-02-06 22:25:28 UTC 
Same issue on openSUSE 13.1 with KDE 4.12.1
Comment 8 Andrew Crouthamel 2018-11-11 04:30:44 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Djuro Drljaca 2018-11-11 07:54:29 UTC 
I recommend that you close the issue. I no longer have a setup where I could try to reproduce this.

If this issue still exist (it was reported for KDE4) then someone will report it again :)
Comment 10 Andrew Crouthamel 2018-11-12 03:16:27 UTC 
Thanks for the update!