bk138
commented
2 years ago Thumbs up for this very good bug report!
Can't repro this though with a minimal x0tigervncserver example, at least on Debian 11. Here's what I did:
$ apt install tigervnc-standalone-server #YYMV for Fedora
$ x0tigervncserver -rfbport 5901 -SecurityTypes TLSVnc -verbose -localhost no
You will require a password to access your desktops.
Password:
Verify:
Would you like to enter a view-only password (y/n)? n
Starting /usr/bin/X0tigervnc -rfbport 5901 -localhost=0 -SecurityTypes TLSVnc -PasswordFile /home/bk/.vnc/passwd -ClientWaitTimeMillis 30000
New X0tigervnc server 'denkpad:1 (bk)' on port 5901 for display :0.
Use xtigervncviewer -SecurityTypes TLSVnc -passwd /home/bk/.vnc/passwd denkpad:1 to connect to the VNC server.
Connecting with MultiVNC 2.0.3 gives a server log of:
$ cat .vnc/
denkpad:5901.log denkpad:5901.pid passwd
bk@denkpad:~$ cat .vnc/denkpad\:5901.log
Sun Dec 5 12:41:42 2021
Geometry: Desktop geometry is set to 1920x1080+0+0
XDesktop: XTest extension present - version 2.2
Main: Listening on port 5901
3NI3X0 New X0tigervnc server 'denkpad:1 (bk)' on port 5901 for display :0.
3NI3X0 Use xtigervncviewer -SecurityTypes TLSVnc -passwd /home/bk/.vnc/passwd denkpad:1 to connect to the VNC server.
Sun Dec 5 12:41:49 2021
Connections: accepted: 192.168.42.160::37896
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VeNCrypt(19)
SVeNCrypt: Client requests security type TLSVnc (258)
Sun Dec 5 12:41:55 2021
XDesktop: Enabling 8 buttons of X pointer device
XDesktop: Allocated shared memory image
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
VNCSConnST: Client pixel format depth 24 (32bpp) little-endian bgr888
Sun Dec 5 12:42:00 2021
VNCSConnST: closing 192.168.42.160::37896: Clean disconnection
EncodeManager: Framebuffer updates: 1
EncodeManager: Tight:
EncodeManager: Solid: 4 rects, 2.07344 Mpixels
EncodeManager: 64 B (1:129591 ratio)
EncodeManager: Indexed RLE: 1 rects, 160 pixels
EncodeManager: 123 B (1:5.30081 ratio)
EncodeManager: Total: 5 rects, 2.0736 Mpixels
EncodeManager: 187 B (1:44355.4 ratio)
TLS: TLS session wasn't terminated gracefully
Connections: closed: 192.168.42.160::37896
ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio)
First theory:
- Fedora 35 removed some TLS ciphers in either OpenSSL or GnuTLS. Found https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2 which hints at https://pagure.io/fedora-docs/release-notes/issue/470 which has https://pagure.io/fedora-docs/release-notes/issue/470#comment-693309
Few things to do:
- Can you try with the above x0tigervncserver commandline as well?
- Please post the output of
ldd /usr/bin/X0tigervnc - Can you try with the change highlighted in https://pagure.io/fedora-docs/release-notes/issue/470#comment-693309 ?
basilrabi
uttarayan21
gujjwal00
Is your bug report about the Desktop Multivnc or the Mobile MultiVNC?
Which MultiVNC version are you using? 2.0.1 (F-Droid) 2.0.3 (Google Playstore)
Describe the bug I am unable to connect to fedora 35 with tigervnc. It only returns "VNC connection failed!"
Log: MultiVNC
This is the log while connecting via MultiVNC
Log: VNC Viewer
This is the log when connecting via VNC Viewer in android
Config
To Reproduce
Expected Behavior Able to connect without error
For the Mobile Version (please complete the following information):