sunarowicz

Exactly the same problem here. Is there any solution available?

Thank you for looking at this. I tried your hint on using the software renderer, but it doesn't have any substantial impact. There is a slightly improvement, but really negligible....

Just want to let know that the problem has solved by its own. I used the scrcpy again after couple of days and it runs pretty fine as for now....

Still no success with Viber. Currently trying to run the appimage. All libraries found, but a ton of symbol errors and warnings there. Any hope this could be addressed? ```...

Thank you for your support! I tried. There is clearly an improvement, but some symbol warnings and one error at the end still persist. Viber does not launch. I will...

Thank you, but unfortunately it doesn't seem your last change had any impact. ``` tux@rock5b ~/D/viber> box64 ./viber.AppImage Dynarec for ARM64, with extension: ASIMD AES CRC32 PMULL ATOMICS PageSize:4096 Running...

Still no success with Viber here. After today's update, the box64 output has changed significantly. Not sure if it is good or bad news... ``` tux@rock5b ~/D/viber> box64 ./viber.AppImage Dynarec...

Ugh, sorry, you are right, FEX-emu has somehow messed the box64 output. Don't understand why, because I'm trying to launch Viber using box64 still in the same way. And this...

Thank you, I'm looking forward to do next try to Launch Viber. FEX experiment? Unsuccessful. Viber did not launch. And because my primary intention always has been to be able...

Thank you so much! But still no go, unfortunately. It seems to me, that the `xcb_randr_monitor_info_next` symbol still makes the trouble. Wouldn't it help to uncomment it in [src/wrapped/wrappedlibxcbrandr_private.h](https://github.com/ptitSeb/box64/commit/47057f076a04693fe2f01dcb9abcbab2eb72a933#diff-b15124a89e435c6e17130211a996b7cf86d0d4f37028aa19fcea720fdbe15d3e)? Or...