search

hanzelpeter / dispmanx_vnc

VNC Server for Raspberry PI using dispmanx
105 stars 52 forks source link

"bad xrle data" #22

Open Spongman opened 6 years ago

Spongman commented 6 years ago

if i connect to dispmanx_vnc with realvnc viewer 6.17.1113 using 8-bit mode, then the client repeatedly complains with an error message "bad xrle data" and disconnects/reconnects.

this doesn't happen with any other vnc server i have tried.

hanzelpeter commented 6 years ago

Hello. I have been able to reproduce issue with realvnc viewer. But it is strange as it happens only when I am connected through wifi to raspberry pi. Once I connected via LAN cable the issue has gone.

Can you write me if you are connected through wifi to raspberry pi. I suspect this has something todo with net speed. But when I am on wifi I can normally operate through xtightvncviewer. Strange issue, also google on "bad xrle data" doesn't give much help.

Spongman commented 6 years ago

I was seeing it connected via LAN only. I don't have any reason to believe the connection is bad in any way. I use it for media streaming and it works fine for that.

fernandog commented 5 years ago

Also having issues while in wireless connection.

hanzelpeter commented 5 years ago

Happened with realvnc viewer and LAN connection but only for quick picture change (hello_tiger demo)

n0valis commented 5 years ago

I am having the same issue via Wifi only connecting to a Raspi OpenElec. Any advice how to solve this?

Update: Ok found it: Options -> Quality: change from Automatic to anything else

domdorn commented 5 years ago

thx @n0valis : Indeed, changing the settings in RealVNC Viewer to just "high" worked for me as well!

joanEstrada commented 1 year ago

2023 and still working. That's weird and clearly a VNC bug.

inspector71 commented 11 months ago

I have experienced this bug many times with a version of dispmanx_vnc bundled into a Kodi Add-On.

Unsure if this helps but the work around I apply is to drop the colour depth down to "Hundreds of colours".

So, I'm not convinced this has anything to do with network connection type. It might do, but network connection type might also be a red herring.

I too get this error using RealVNC Viewer, albeit a version that nags the least.

vncviewer_IfqYkBQbF8

In case this helps debug the issue, though perhaps more likely for RealVNC than the server, whilst already connected, in Hundreds of colours mode, if I attempt to change the slider to a higher setting, I get this:

vncviewer_pF1K6E33Og

However, Tight VNC ...

tvnviewer_jaC1aAeV5V

... with these settings:

tvnviewer_Z3ONX4rhiG

... seems to be fine.