search

careteditor / releases-beta

Caret Beta releases
40 stars 4 forks source link

Segmentation fault on Debian #19

Open Csardelacal opened 4 years ago

Csardelacal commented 4 years ago

This seems to be a similar issue to the one others are having, but mine is not related to libgconf. Reinstalling the beta Caret package didn't help.

The only output I get is Segmentation fault, the program doesn't continue. I'm running Debian on the testing channel. The app runs fine on Fedora 30.

astoilkov commented 4 years ago

Hi,

Does Caret non-beta release work? Have the same thing happened with other apps (for example other Electron-based apps like VSCode, Slack)?

Have you seen the two issues below which also mention errors related to libgconf?

Thank you for your cooperation.

Csardelacal commented 4 years ago

Electron based apps like VS Code, Atom and Todoist work fine. This seems to not be the issue.

Downgrading to stable works.

It's not related to libgconf. System halts immediately with the message "Segmentation fault", there's no console output except for that.

Von: Antonio Stoilkov notifications@github.com Gesendet: Samstag, 26. Oktober 2019 14:39 An: careteditor/releases-beta releases-beta@noreply.github.com Cc: César de la Cal flunsidelacal@msn.com; Author author@noreply.github.com Betreff: Re: [careteditor/releases-beta] Segmentation fault on Debian (#19)

Hi,

Does Caret non-beta release work? Have the same thing happened with other apps (for example other Electron-based apps like VSCode, Slack)?

Have you seen the two issues below which also mention errors related to libgconf?

Thank you for your cooperation.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/careteditor/releases-beta/issues/19?email_source=notifications&email_token=AAIZON6TJTVU7OCJQF5ZSJLQQQ3ADA5CNFSM4JFE6SWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECKHCNY#issuecomment-546599223, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAIZON6PXTC6RVE3TMOUM2LQQQ3ADANCNFSM4JFE6SWA.

astoilkov commented 4 years ago

Thank you very much. I wrongly read the message that it was related to libgconf. Sorry for the misunderstanding.

If we use the same Electron version as the other Electron apps everything should be fine. We will investigate. Thanks!

RogueScholar commented 4 years ago

For what it's worth, I used a dirty workaround and just replaced the libnode.so file in /usr/share/caret-beta with a known working one from another Electron app I use called Zenkit. It was literally as simple as:

sudo mv /usr/share/caret-beta/libnode.so /usr/share/caret-beta/libnode.so.bak
sudo cp /opt/Zenkit/libnode.so /usr/share/caret-beta
sudo chown root:root /usr/share/caret-beta/libnode.so
sudo chmod 0755 /usr/share/caret-beta/libnode.so

These days, it's hard to imagine any legit PC user getting along without a few genuflections to the Electron Gods installed already...especially if they're using Linux. It took me a couple tries, copying in the libnode.so file from various apps I have resident to find one that brought the magician to the birthday party. :wink: You can get a printout of all the libnode.so files on your system complete with mtime and size with the following command line fu:

sudo find / -type f -name 'libnode.so' -exec ls -la '{}' \;

My sample size was too small to be very instructive, but I approached the list from newest to oldest, skipping any of them that were more than 1MiB different in size from the one that ships with Caret (which of course also appears in the list for easy comparison). Could just as easily have been dumb luck, but I got it working on the second attempt following that rubric. Hope this helps someone else along the way.