noVNC error: Incomplete zlib block for interactive desktop sessions

Hello,

Some users are getting the ‘incomplete zlib block’ error when using interactive desktop. desktop is a Nvidia GPU server running Rocky Linux 8.8. ood version is 3.


the issue appears when the user double clicks something within the session. the error is persistent and stays on the screen but the interactive session keeps working.

From the error, I could find that error originates from the following file: https://github.com/OSC/ondemand/blob/master/apps/dashboard/public/noVNC-1.3.0/core/inflator.js

But I couldn’t understand the reason behind it.
not sure what else information I need to provide. please let me know of any potential resolutions.

thanks

I’m not entirely sure what could cause this - I don’t think I’ve ever seen it before. The upstream project [1] has no issue for the same, suggesting they’ve never seen it.

I’d wonder if there is anything relevant in vnc.log. You can find it here in the session’s directory.

  1. GitHub - novnc/noVNC: VNC client web application

Hi, thanks for the response. Upon further investigation, the issue seems to be related to some firefox browsers of some users. Other users seems to be using firefox just fine and couldn’t reproduce the issue. In summary, it appears to be a browser issue than an OOD issue. thanks for the help.

@jeff.ohrstrom Not the OP but we are having the same issue. AlmaLinux 8.8 + OOD 3.0.3

But this does not seem to be a browser or some caching issue as both Firefox and Chrome display the same error.

This seems to be triggered when selecting text and can be reproduced. I verified SELinux and Firewall and they are happy. No logs are generated by VNC(log pasted below the message) and I don’t see any error logs related to this in either apache or phusion.

Interestingly, this does not seem to be an issue on Almalinux 9 + 3.0.1 which we are using as a dev instance. For now, we made the dev instance available to users while we are investigating this. So far, we have no solution.

TurboVNC Server (Xvnc) 64-bit v3.0.91 (build 20230818)
Copyright (C) 1999-2023 The VirtualGL Project and many others (see README.md)
Visit http://www.TurboVNC.org for more information on TurboVNC

16/10/2023 10:53:43 Using security configuration file /etc/turbovncserver-security.conf
16/10/2023 10:53:43 Enabled security type 'tlsvnc'
16/10/2023 10:53:43 Enabled security type 'tlsotp'
16/10/2023 10:53:43 Enabled security type 'tlsplain'
16/10/2023 10:53:43 Enabled security type 'x509vnc'
16/10/2023 10:53:43 Enabled security type 'x509otp'
16/10/2023 10:53:43 Enabled security type 'x509plain'
16/10/2023 10:53:43 Enabled security type 'vnc'
16/10/2023 10:53:43 Enabled security type 'otp'
16/10/2023 10:53:43 Enabled security type 'unixlogin'
16/10/2023 10:53:43 Enabled security type 'plain'
16/10/2023 10:53:43 Desktop name 'TurboVNC: ceres19-compute-54.scinet.local:3 (yasasvy.nanyam)' (ceres19-compute-54.scinet.local:3)
16/10/2023 10:53:43 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
16/10/2023 10:53:43 Listening for VNC connections on TCP port 5903
16/10/2023 10:53:43   Interface 0.0.0.0
16/10/2023 10:53:43 Framebuffer: BGRX 8/8/8/8
16/10/2023 10:53:43 New desktop size: 800 x 600
16/10/2023 10:53:43 New screen layout:
16/10/2023 10:53:43   0x00000040 (output 0x00000040): 800x600+0+0
16/10/2023 10:53:43 Maximum clipboard transfer size: 1048576 bytes
16/10/2023 10:53:43 VNC extension running!

16/10/2023 10:53:52 Got connection from client 127.0.0.1
16/10/2023 10:53:53 Normal socket connection
16/10/2023 10:53:53 Using protocol version 3.8
16/10/2023 10:53:53 Enabling TightVNC protocol extensions
16/10/2023 10:53:53 Advertising Tight auth cap 'VENCRYPT'
16/10/2023 10:53:53 Advertising Tight auth cap 'VNCAUTH_'
16/10/2023 10:53:53 Advertising Tight auth cap 'ULGNAUTH'
16/10/2023 10:53:53 Full-control authentication enabled for 127.0.0.1
16/10/2023 10:53:53 Pixel format for client 127.0.0.1:
16/10/2023 10:53:53   32 bpp, depth 24, little endian
16/10/2023 10:53:53   true colour: max r 255 g 255 b 255, shift r 0 g 8 b 16
16/10/2023 10:53:53 Using tight encoding for client 127.0.0.1
16/10/2023 10:53:53 rfbProcessClientNormalMessage: ignoring unknown encoding -260 (fffffefc)
16/10/2023 10:53:53 Using JPEG subsampling 0, Q100 for client 127.0.0.1
16/10/2023 10:53:53 Enabling Desktop Size protocol extension for client 127.0.0.1
16/10/2023 10:53:53 Enabling LastRect protocol extension for client 127.0.0.1
16/10/2023 10:53:53 Enabling QEMU Extended Key Event protocol extension for client 127.0.0.1
16/10/2023 10:53:53 Enabling Extended Desktop Size protocol extension for client 127.0.0.1
16/10/2023 10:53:53 rfbProcessClientNormalMessage: ignoring unknown encoding -309 (fffffecb)
16/10/2023 10:53:53 Enabling Fence protocol extension for client 127.0.0.1
16/10/2023 10:53:53 Enabling Continuous Updates protocol extension for client 127.0.0.1
16/10/2023 10:53:53 rfbProcessClientNormalMessage: ignoring unknown encoding -307 (fffffecd)
16/10/2023 10:53:53 Enabling Extended Clipboard protocol extension for client 127.0.0.1
16/10/2023 10:53:53 rfbProcessClientNormalMessage: ignoring unknown encoding 1464686180 (574d5664)
16/10/2023 10:53:53 Enabling full-color cursor updates for client 127.0.0.1
16/10/2023 10:53:53 Using Tight compression level 1 for client 127.0.0.1
16/10/2023 10:53:53 WARNING: Disabling QEMU Extended Key Event extension because neither LED state
16/10/2023 10:53:53   extension is supported by the client.
16/10/2023 10:53:53 Using 4 threads for Tight encoding
16/10/2023 10:53:53 Client clipboard capabilities:
16/10/2023 10:53:53 - Plain text (limit = 0 bytes)
16/10/2023 10:53:53 Continuous updates enabled
16/10/2023 10:53:53 New desktop size: 1512 x 859
16/10/2023 10:53:53 New screen layout:
16/10/2023 10:53:53   0x00000000 (output 0x00000040): 1512x859+0+0
16/10/2023 10:53:53 Continuous updates enabled
16/10/2023 10:53:54 Continuous updates enabled
16/10/2023 10:53:54 Continuous updates enabled

We haven’t moved to EL8 so I can’t really replicate.

I would wonder if websockify update can help?

I’d also wonder if different browsers could help at least explain the issue.

Also happening with our user base. This error is client side and probably related to browser they are using. Had 1 user duplicate based on cut & paste operation of csv data, and another user interacting in the UI (moving windows adound). Error code is same with a slight difference

Has anyone looked at using novnc 1.4.0?

Can Confirm this is happening in Google Chrome right now for one user.

One solution we found was to set some level of compression. No compression triggers that error.

YES! That tracks! Our users who experienced this were not using compression. Thanks @ynanyam!