Philipp Hahn

- [WayVNC](https://github.com/any1/wayvnc) - [ ] Need to check why you get back a `PSEUDO_QEMU_EXTENDED_KEY_EVENT` instead of the `RAW` screen.

Please provide more information: - You're using the **synchronous** API, which is still experimental, but your log-output-format looks different: it includes time stamp information, so I assume using `vncdotool` is...

Please provide more information, especially which VNC **server** you're connecting to. Also: with which arguments you call `vncdotool` respective what commands to you send? Does the disconnect happen early or...

This first part is not required as this is Python and not Java: No need to add that property as `self.name` can be accessed directly in `client.py`: ```python def get_server_name(self)...

Probably fixed by #289

> INFO:twisted:Protocol version 4.000 not supported See https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm?turl=WordDocuments%2Fkvmandintelamt.htm for some details from intel plus https://community.intel.com/t5/Intel-Business-Client-Software/RFB-VNC-protocol-4-0-specification/m-p/763420/highlight/true#M25 With #243 now merged adding support for AMT should be simple or might already work....

What might be wrong?

> b'RFB 003.008\n' Hello, I'm a RFB server talking protocol version 3.008. > b'\x01\x01' I offer a single authentication mechanism, which is AuthTypes.NONE > b'\x00\x00\x00\x01\x00\x00\x00\x00\x04\x00\x03\x00\xff\xff\xff!' And now I'm pissed because...

Probably a network issue, after which the data gets interpreted wrongly: > 2023-07-13 18:00:24 [WARNING] 'Timed Out', retrying in 0 seconds... But `` is also not implemented; basically only ``...

While refactoring `vncdotool` I already had some quick thoughts on adding support for other encoding as `vncdotool` currently only supports `RAW`. - You would have to extend `vncdotool.rfb.RFBClient._handleRectangle()` to handle...