Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Compatibility issues - Android 12; version 2.1.5 (and 2.1.6 via Google Play) #245

Closed
JOs86 opened this issue Oct 17, 2024 · 11 comments
Closed

Comments

@JOs86
Copy link

JOs86 commented Oct 17, 2024

Mobile (Android): Android 12
Version: 2.1.5, 2.1.6
HW: Samsung S10+ (Exynos 9820)
Model: SM-G975F
API: 31
One UI: 4.1
Google Play Services: 24.40.35
[2.1.6] Installed from Play Store, [2.1.5] from F-Droid

  • VNC server vendor: TigerVNC
  • VNC server version: 1.12.0+dfsg-8
  • OS version: Debian 12 (Bookworm) via proot-distro [and termux]
  • OS language: English (US)
  • Xorg version used: 2:21.1.7-3+deb12u7

Issue / Description

  • Compatibility issue on Android 12
  • Message: Error! VNC connection setup failed!

To Reproduce

@JOs86 JOs86 added the bug label Oct 17, 2024
@JOs86
Copy link
Author

JOs86 commented Oct 17, 2024

Screenshot_20241017_131716

@JOs86
Copy link
Author

JOs86 commented Oct 17, 2024

Steps to reproduce the behavior:

  1. Go to F-Droid or Google Play
  2. Install and update MultiVNC (see the version above, i.e. 2.1.5, resp. 2.1.6)
  3. Follow the termux and proot documentation and proceed to establish a connection.
  4. Assumptions: X11 is working, other VNC sulutions are working.
  5. Configure MultiVNC and connect

Expected Behavior
Connection established and successful.

@JOs86
Copy link
Author

JOs86 commented Oct 17, 2024

Additional context
Resolution change in Android settings might be part of the problem, simply changing it back does not necessarily solve the issue. However, other solutions (VNC or not) are working correctly.
Concerning the server -> Proot enviroment might be tricky and complex.
I.e. parameter -geometry, etc. =>
[In Termux]
export XDG_RUNTIME_DIR=${TMPDIR}
proot-distro login debian --user root --shared-tmp

[In Proot, i.e. proot-distro]

root@localhost:~# export XDG_RUNTIME_DIR=${TMPDIR}

root@localhost:~# vncserver -geometry 1600x900 -xstartup /usr/bin/startxfce4 :0

Additional logs might be necessary to determine the exact cause due to complexity.

@JOs86
Copy link
Author

JOs86 commented Oct 17, 2024

Other versions:
2.1.3 -> ok
2.1.4 -> mostly ok

@bk138
Copy link
Owner

bk138 commented Oct 18, 2024

Can repro, it's most likely due to an SSL change.

@JOs86
Copy link
Author

JOs86 commented Oct 20, 2024

Excellent, thanks a lot in advance..

@bk138
Copy link
Owner

bk138 commented Oct 20, 2024

findings

  • most likely due to the inadvertent libressl update in 52afd2d
  • 13791e5 is ok for instance
  • reverting to old LibreSSL version worked

good log

2024-10-20 20:59:17.301  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  com.coboltforge.dontmind.multivnc.VNCConn@8b76b10: setupClient()
2024-10-20 20:59:17.301  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  com.coboltforge.dontmind.multivnc.VNCConn@8b76b10: rfbInit() setting up direct connection
2024-10-20 20:59:17.301  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  com.coboltforge.dontmind.multivnc.VNCConn@8b76b10: rfbInit() about to connect to '10.0.2.2', port 5903, repeaterId 5900
2024-10-20 20:59:17.306  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  VNC server supports protocol version 3.8 (viewer 3.8)
2024-10-20 20:59:17.307  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  We have 2 security types to read
2024-10-20 20:59:17.307  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  0) Received security type 19
2024-10-20 20:59:17.307  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Selecting security type 19 (0/2 in the list)
2024-10-20 20:59:17.307  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  1) Received security type 2
2024-10-20 20:59:17.307  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Selected Security Scheme 19
2024-10-20 20:59:17.308  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Got VeNCrypt version 0.2 from server.
2024-10-20 20:59:17.308  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  We have 2 security types to read
2024-10-20 20:59:17.308  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  0) Received security type 2
2024-10-20 20:59:17.308  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  1) Received security type 258
2024-10-20 20:59:17.308  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Selecting security type 258
2024-10-20 20:59:17.309  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  OpenSSL version LibreSSL 3.0.1 initialized.
2024-10-20 20:59:17.311  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  TLS session initialized.
2024-10-20 20:59:21.670  7576-7690  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Reading password failed

bad log

2024-10-20 21:09:45.646  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  com.coboltforge.dontmind.multivnc.VNCConn@4633f: setupClient()
2024-10-20 21:09:45.646  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  com.coboltforge.dontmind.multivnc.VNCConn@4633f: rfbInit() setting up direct connection
2024-10-20 21:09:45.646  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  com.coboltforge.dontmind.multivnc.VNCConn@4633f: rfbInit() about to connect to '10.0.2.2', port 5903, repeaterId 5900
2024-10-20 21:09:45.659  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  VNC server supports protocol version 3.8 (viewer 3.8)
2024-10-20 21:09:45.659  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  We have 2 security types to read
2024-10-20 21:09:45.659  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  0) Received security type 19
2024-10-20 21:09:45.660  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Selecting security type 19 (0/2 in the list)
2024-10-20 21:09:45.660  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  1) Received security type 2
2024-10-20 21:09:45.660  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Selected Security Scheme 19
2024-10-20 21:09:45.660  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Got VeNCrypt version 0.2 from server.
2024-10-20 21:09:45.661  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  We have 2 security types to read
2024-10-20 21:09:45.661  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  0) Received security type 2
2024-10-20 21:09:45.661  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  1) Received security type 258
2024-10-20 21:09:45.661  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  Selecting security type 258
2024-10-20 21:09:45.664  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    I  OpenSSL version LibreSSL 3.8.2 initialized.
2024-10-20 21:09:45.670  8119-8210  VNCConn-native          com.coboltforge.dontmind.multivnc    E  com.coboltforge.dontmind.multivnc.VNCConn@4633f: rfbInit() connection failed. Cleanup by library.

bk138 added a commit that referenced this issue Oct 20, 2024
Was inadvertantly updated in 52afd2d

Fixes #245, but we'd want a solution that works with newer LibreSSL as well...
@bk138 bk138 closed this as completed Oct 20, 2024
bk138 added a commit to LibVNC/libvncserver that referenced this issue Oct 20, 2024
bk138 added a commit that referenced this issue Oct 20, 2024
@aRTee42
Copy link

aRTee42 commented Oct 22, 2024

Just FYI, Android / F-Droid Multi-VNC V2.1.7 still has this bug (I reported duplicate 246). Based on the above discussion, I was under the impression that the fix should have been there, or am I misunderstanding things?

@bk138
Copy link
Owner

bk138 commented Oct 22, 2024

Just FYI, Android / F-Droid Multi-VNC V2.1.7 still has this bug (I reported duplicate 246). Based on the above discussion, I was under the impression that the fix should have been there, or am I misunderstanding things?

v2.1.8 has the fix, see https://github.com/bk138/multivnc/blob/master/android/ChangeLog.md :-)

@aRTee42
Copy link

aRTee42 commented Oct 22, 2024

Thanks a lot, just waiting for F-Droid to offer the update.

@JOs86
Copy link
Author

JOs86 commented Oct 22, 2024

FYI: It worked for me.. (on Android 12)

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants