Andri Yngvason

I still think that it's inaccurate to say the RealVNC isn't supported when it works just fine.

It works fine on sway, so I think it's a wayfire bug.

I haven't had the time to look into this, and it's not very high on my list of priorities.

> @any1 I found some more info about the issue. It seems it's not a way fire bug but an issue with wlroots. There is this issue describing the changes...

Ahh, it's because wayfire doesn't map the seat to the output: https://github.com/WayfireWM/wayfire/issues/1283

Coercing the software rendering pixel format to a 32 bit one instead of 24 will not change the GPU buffer format into a 32 bit one as well. It's still...

Partial writes and errors need to be handled better here: https://github.com/any1/wayvnc/blame/master/src/data-control.c#L199 Have you tried making sure that your clipboard is empty when you connect?

Is this still an issue with the newest release? Was there anything more after the last error? Could it be that you don't have core dumps enabled on your system?

Multiple monitors in the same client window are not implemented yet, although you can cycle between them using a key binding of your own choice. See: https://github.com/any1/wayvnc/issues/112#issuecomment-1312663912

Yeah, this is planned, but it looks like I didn't make an issue for it. The main hurdles are the following: * There does not exist a protocol extension for...