Emanuele D'Osualdo

@pl-semiotics thanks for the remarks. In which ways the workaround could cause problems? Do you think simlinking the old version to the new one would work? Would linking the library...

I got the update and can confirm that `ln /usr/lib/libcrypto.so.1.1 /usr/lib/libcrypto.so.1.0.2` works on my RM1. I do not know if there are bad side effects of using the "wrong" version....

> The real trouble is that there was a bunch of API/ABI breakage in libcrypto 1.1 Yes I was checking that as well...the symlinking seemed to work at first, but...

> libcrypto is only being used by the few functions on the rm2. Ok now everything makes more sense! I was puzzled by the fact that symlinking the old library...

@pl-semiotics any update on this?

In case it helps, the new toolchains have been published: https://discord.com/channels/385916768696139794/386181213699702786/830914172640428053 > reMarkable 1: https://storage.googleapis.com/remarkable-codex-toolchain/codex-x86_64-cortexa9hf-neon-rm10x-toolchain-3.1.2.sh > reMarkable 2: https://storage.googleapis.com/remarkable-codex-toolchain/codex-x86_64-cortexa7hf-neon-rm11x-toolchain-3.1.2.sh

@corwin-of-amber that sounds like issue #5 : the current version is not compatible with rm2fb, so you have to uninstall/deactivate rm2fb before running the vnc server

@pl-semiotics gentle ping: can I help with anything to get this sorted?

@pl-semiotics thank you so much for your amazing work! I only have RM1, I'll try to recruit somebody for testing on RM2. I will look at this next weekend.

Thanks for the report! This looks strange. The highlighting is handled a bit specially because the PDF generation backend does not understand blend modes (which are the way the tabled...