Now I’m not sure if my problem have anything to do with yours. My problem started maybe 1.5-2 weeks ago. I cant use KRDC or Remmina from Leap42.1 clients to connect to my 13.1 server any longer. The connection window just disappears(on the client side).
It is impossible to start remote control in YaST2(ok the server swallow it but if you reopen the function again it's still disabled).
So what may be wrong? I have no idea, here is how the /root/.vnc/servername:3.log look in the 13.1 server after have run the command vncserver in a terminal:
Code:
hu Dec 17 17:34:46 201
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5903
vncext: Listening for HTTP connections on all interface(s), port 5803
vncext: created VNC server for screen 0
..
Trying to connect from Leap42.1/KRDC/Remmina clients to 13.1 server:
Code:
Thu Dec 17 17:47:15 2015
Connections: accepted: 192.168.0.28::36577
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VeNCrypt(19)
TLS: TLS Handshake failed: Could not negotiate a supported cipher
suite.
TLS: TLS session wasn't terminated gracefully
SConnection: AuthFailureException: TLS Handshake failed
Connections: closed: 192.168.0.28::36577 (TLS Handshake failed)
Trying to connect to a 42.1 server and /root/.vnc/servername:1.log after have run the command vncserver in a terminal:
Code:
Thu Dec 17 17:53:43 2015
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: Listening for HTTP connections on all interface(s), port 5801
vncext: created VNC server for screen 0
..
Trying to connect from Leap42.1/KRDC/Remmina clients to 42.1 server:
Code:
Thu Dec 17 17:59:28 2015
Connections: accepted: 192.168.0.28::53399
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VeNCrypt(19)
SVeNCrypt: Client requests security type TLSVnc (258)
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/Xvnc (xorg_backtrace+0x48) [0x5aa268]
(EE) 1: /usr/bin/Xvnc (0x400000+0x1ae099) [0x5ae099]
(EE) 2: /lib64/libpthread.so.0 (0x7faaec720000+0xf890) [0x7faaec72f890]
(EE) 3: /lib64/libpthread.so.0 (pthread_mutex_lock+0x4) [0x7faaec72a244]
(EE) 4: /usr/lib64/libgnutls.so.28 (0x7faaed8f4000+0x47b4c) [0x7faaed93bb4c]
(EE) 5: /usr/lib64/libgnutls.so.28 (0x7faaed8f4000+0xd9507) [0x7faaed9cd507]
(EE) 6: /usr/lib64/libgnutls.so.28 (0x7faaed8f4000+0xd7619) [0x7faaed9cb619]
(EE) 7: /usr/lib64/libgnutls.so.28 (gnutls_dh_params_generate2+0x19) [0x7faaed9$
(EE) 8: /usr/bin/Xvnc (_ZN3rfb12SSecurityTLS9setParamsEP18gnutls_session_int+0x$
(EE) 9: /usr/bin/Xvnc (_ZN3rfb12SSecurityTLS10processMsgEPNS_11SConnectionE+0x1$
(EE) 10: /usr/bin/Xvnc (_ZN3rfb14SSecurityStack10processMsgEPNS_11SConnectionE+$
(EE) 11: /usr/bin/Xvnc (_ZN3rfb17SSecurityVeNCrypt10processMsgEPNS_11SConnectio$
(EE) 12: /usr/bin/Xvnc (_ZN3rfb11SConnection18processSecurityMsgEv+0x2c) [0x52a$
(EE) 13: /usr/bin/Xvnc (_ZN3rfb16VNCSConnectionST15processMessagesEv+0x87) [0x5$
(EE) 14: /usr/bin/Xvnc (_ZN14XserverDesktop17readWakeupHandlerEP6fd_seti+0x209)$
(EE) 15: /usr/bin/Xvnc (vncCallReadWakeupHandlers+0x2a) [0x50f49a]
(EE) 16: /usr/bin/Xvnc (0x400000+0x11582c) [0x51582c]
(EE) 17: /usr/bin/Xvnc (WakeupHandler+0x6d) [0x560bed]
(EE) 18: /usr/bin/Xvnc (WaitForSomething+0x1ee) [0x5a76be]
(EE) 19: /usr/bin/Xvnc (Dispatch+0x9d) [0x55c0bd]
(EE) 20: /usr/bin/Xvnc (dix_main+0x3b5) [0x560135]
(EE) 21: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7faaebb00b05]
(EE) 22: /usr/bin/Xvnc (0x400000+0x51eee) [0x451eee]
(EE)
(EE) Segmentation fault at address 0x10
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
after 223 requests (223 known processed) with 0 events remaining.
The X11 connection broke (error 1). Did the X11 server die?
qwebyast: Fatal IO error: client killed
kdeinit5: Fatal IO error: client killed
I can use the clients to connect to RDP servers (even linux WM's under Virtualbox) and I can use a web browser to connect server ip:5803 (13.1 server(but not the 42.1)). I havent try to put any energy in to it but it semms that the vnc client have some problems as well.
Anyone else with similar problems? Maybe time for a bug report then.
regards
VNC server on 42.1 - currently no way?
Re: VNC server on 42.1 - currently no way?
utput(Id: 60 , Name: "VNC-0" ) ( "VNC-0" ) to KScreen:
Originally Posted by suse_rasputin
Bookmarks