remarkable2-framebuffer: Segmentation fault with version 0.0.6

I just upgraded my Remarkable to version 2.9.0.210 and remarkable2-framebuffer to version 0.0.6 which is supposed to be compatible, but I get:

308 Segmentation fault

However, with the previous version emarkable2-framebuffer 0.0.5 I have no problems with version 2.9.0.210 of my Remarkable.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 17

Most upvoted comments

Thanks for working on the PR! I’m closing this since it’s not directly caused by rm2fb.

matteodelabre on Aug 13, 2021

Sure, I leave my comments in the PR. Thanks to @matteodelabre

juanfcocontreras on Aug 13, 2021

(using xochitl may work, but will probably also kill the real Xochitl).

You’d be correct, if you don’t have $NO_XO set, it will kill the real xochitl instance. I’m working on handling that.

Eeems on Aug 13, 2021

I just saw that @Eeems eems is making a pull request that fixes these problems. Thank you very much!

Just commenting on the same question I just asked to @matteodelabre , there are more references to remarkable-shutdown (rm-shutdown) in that script. They should all be changed, right?

Correct, I’m writing the changes now.

Eeems on Aug 13, 2021

Looks like remarkable-autoinstall was never updated to use xochitl as the server and is still using remarkable-shutdown:

https://github.com/ddvk/remarkable-autoinstall/blob/master/rm2/scripts/ko.sh#L11

Edit: It also looks like @juanfcocontreras also opened an issue about this: https://github.com/ddvk/remarkable-autoinstall/issues/17

Eeems on Aug 13, 2021