Caret Beta does not start under Ubuntu 18.10

[Torsten-K]

Caret Beta does not start any longer under Xubuntu 18.10 (= Ubuntu with Xfce desktop environment), while it used to work under 18.04. This is what the terminal outputs:

Memory access error (memory dump written)

Caret 3.4.6 works, however. Any ideas what could be wrong?

[astoilkov]

We will investigate this and get back to you. Thanks for reporting this.

[HaxorGaruda]

same on ParrotOs debian testing.. it's got segmentation fault..

[HaxorGaruda]

[leandrojmp]

I am having the same problem, I think it is related to these issues electron/electron#14541 and electron/electron#13972 in the electron repository.

The poblem seems to be related to libnode.so, I made a little test and copied the libnode.so from another electron app (vs code) that is working in my system to the caret-beta folder and the app worked, didn't used it a lot yet, but it seems to be working fine.

[astoilkov]

@leandrojmp Thank you so much for the investigation. We will keep an eye on the issue and see what we can do. Thanks again!

[gibranlp]

I can confirm that this works on Fedora 29.

In my case i had to copy 2 files, libXss.so.1 and libnode.so, from another electronapp(atom) and now it works.

Awesome!!

[Torsten-K]

Thanks for the hint, @gibranlp. Copying libnode.so from Atom did the trick for me on Xubuntu 19.04 (Disco Dingo, development branch). It should work on 18.10, too.
sudo cp /usr/share/atom/libnode.so /usr/share/caret-beta/

[axelitus]

I got the same error in Ubuntu 18.10 and the workaround shared by @leandrojmp worked. I had to copy libnode.so from the Atom installation. Hopefully this get fixed on the next beta release.

[Torsten-K]

The bug hasn’t been fixed already in Caret Beta Version 4.0.0-rc23, but the workarounds posted by @leandrojmp and @gibranlp still seem to work in this version.

[Torsten-K]

After upgrading to Xubuntu 19.10 (dev):
/usr/share/caret-beta/caret-beta: symbol lookup error: /usr/share/caret-beta/caret-beta: undefined symbol: udata_setCommonData_59

The full version 3.4.6 works, however.

Is the software still under development, anyway? No new versions since February or so, no comments from the developers, nothing. Seems quite dead, unfortunately.

[axelitus]

@Torsten-K I don't know about the error, but regarding the status of development I can refer you to this tweet by the Caret team: https://twitter.com/careteditor/status/1136198029357264896

Unfortunately, it seems Caret is not being actively worked on. The upside is that a replacement for it is on the way (but don't know when it will arrive).

[astoilkov]

The new product is almost done – applying final touches. The big task before we release officially is to create the website and the product documentation.

However, it is possible to start sending the product to old clients before the website is fully ready.

[astoilkov]

Regarding the error, it seems this is a bug in Electron fixed in newer versions.

[axelitus]

Great news @astoilkov! Can't wait for the launch!

[gibranlp]

The new product is almost done – applying final touches. The big task before we release officially is to create the website and the product documentation.

However, it is possible to start sending the product to old clients before the website is fully ready.

When will you guys be sending the new software? is this for the clients who have paid for caret?

[Torsten-K]

@gibranlp: In the Tweet @axelitus linked to (https://twitter.com/careteditor/status/1136198029357264896), they say that the licenses from Caret will be valid for the new product. That sounds quite fair.

[Torsten-K]

@astoilkov: These are good news! But why a new product instead a new major version of Caret?

[gibranlp]

@Torsten-K Sounds good getting a new product, instead of an update, i was just asking when can we try this new thing, i'm really looking forward into it.

[astoilkov]

We can't promise any dates when we will start sending to clients. This is because we can't know for sure if the product won't have problems when testing with the first internal group of people. Issues like bugs, UX problems and vital missing features could arise - things we missed.

Indeed licenses from Caret will be valid for the new product.

We are doing a new product because there are some features that we will remove that now exist in Caret. We are also doing rework on some of the UI. All this seems like too big of a shift - there will be some people that don't want to migrate to the new product.