Open DeadNumbers opened 4 years ago
Any ideas?
well, it looks like there is some nil pointer in there :) these situations really need a debugger attached.. remote advice according to an error won't do a lot of good. Would love to be of more help, if you have more info..
I never tested this on archlinux, and more importantly I don't know which vnc server this is working with. Sometimes they use some messages that I haven't programmed in, which makes the decoder derail (this is a binary stream after all), and sometimes there can be a message that sends a legit payload that I have not planned for. In VncProxy I think I have worked out most of these kinks, but this project was never in production. if you manage to debug it, it'll be glad to merge your code back in.
I see Vino is a VNC-Server... I used tight to program this - so that would be a more compatible option if you don't have the time to debug.
@DeadNumbers
It seems that sometimes DefaultClientMessageHandler
is called before the canvas is initialized.
https://github.com/amitbet/vnc2video/blob/9d50b9dab1d92afd6c71ca5ccc5157135c121428/client.go#L37-L49
DefaultClientMessageHandler
is set up and started in line 38 and canvas is set up in line 48.
See #14 for my proposed fix.
Hi! I'm tested this code on Arch Linux, Gnome and Vino (https://wiki.gnome.org/Projects/Vino). Code from
examples/client
Traceback
Sometimes app print desktop name, but sometimes app crashed.