VNC Client for 10iii

Applications
#21

Thanks for the suggestion, but Jolla is not supporting android on Gemini, and I am not experienced enough to compile the missing kernel modules for waydroid. :slight_smile:

#22

No. If you could install it from chum (and not download an RPM and force rpm installation) then all the deps are already satisfied.

If it’s not working something else must be the reason.

1 Like
#23

Yes indeed the chum version.
Maybe I misunderstood the interface. From the pulldown menu, I get “About” & “Connect”

In connect, I can input VNC Server URL, and I have a slider with three options for Quality.

If I enter a server URL such as 192.168.x.y or 192.168.x.y:5900 and proceed by clicking accept, the menu I just was at dissapears to the left, and I just have the classic blurry sailfish background, where I yet again have access to the pulldown menu.

thank for commenting btw

#24

It looks like you’ll have to specify the port as well. Usually that’s 5900.

#25

I tried to specify the port separated by a single colon, but I guess technically since the field is called URI, I should set a protocol prefixing the IP

#26

@poetaster: I tried to find the part in the code, that handles sailjail, but i did not succeed. Could you please give me a hint where I have to look for it?
Thanks in advance,

Lukas

#27

You can copy the file: /usr/share/applications/harbour-vncscreen.desktop to /etc/sailjail/applications/
and add two lines to that file:

[X-Sailjail]
Sandboxing=disabled

#28

Thank you very much for the fast and concrete reply. I will test it on weekend, but I am pretty sure it will work. I will respond here, when done.
BR

Lukas

1 Like
#29

Did anyone ever figure this out? I can’t get this to work. Does anyone have an example of what should the URL look like?

#30

Unfortunately not.
I copied the file as root? Maybe rights and ownership has to be adjusted?
Where have the lines to be pasted? At the very end?

Regards,

Lukas

#31

It looks like the url should use the vnc uri scheme (vnc://user@192.168.x.y:5900). Running the program from commandline I can see why it doesn’t work for me, but I don’t know what the fix would be:

[D] onAccepted:64 - vnc://192.168.x.y:5900
[D] onAccepted:69 - exist0
[D] onAccepted:72 - []
[D] unknown:0 - value type QVariant::uint32_t
[D] unknown:0 - path= "vnc://192.168.x.y:5900" host "192.168.x.y" port 5
900 scheme "vnc"
[D] unknown:0 - quality 0
[D] unknown:0 - server host 192.168.x.y server Port 5900 password ""
[D] unknown:0 - parametri ok= true
[D] unknown:0 - --------------------- trying init ---------------------
[D] unknown:0 - "VNC server supports protocol version 5.0 (viewer 3.8)"
[D] unknown:0 - "We have 5 security types to read"
[D] unknown:0 - "0) Received security type 13"
[D] unknown:0 - "1) Received security type 133"
[D] unknown:0 - "2) Received security type 5"
[D] unknown:0 - "3) Received security type 129"
[D] unknown:0 - "4) Received security type 192"
[D] unknown:0 - "Unknown authentication scheme from VNC server: 13, 133, 5,
129, 192"
[D] unknown:0 - init failed password error false
[D] unknown:0 - finisce il tentativo

The server is using the default authentication (windows password).

#32

It seems the problem is the server is RealVNC, which uses proprietary “security types” which open VNC client implementations can’t support.

If you can, try fiddling with the server settings to allow a non-proprietary authentication scheme (usually called “Vnc auth”).

Reference: Unsupported security types (types: 13,133,5,129,192) ¡ Issue #1041 ¡ novnc/noVNC ¡ GitHub

2 Likes