Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Electron Version too Old

See original GitHub issue
  • I am on the latest version

  • I have searched the issues of this repo and believe that this is not a duplicate

  • OS version and name: Fedora Workstation 31

  • version: 0.32 Dump when I try to start the appimg from CLI:

installed: X-AppImage-BuildId=847a0770-d98f-11a7-0ebd-e5b83ffea09e image: X-AppImage-BuildId=847a0770-d98f-11a7-0ebd-e5b83ffea09e
A JavaScript error occurred in the main process
Uncaught Exception:
Error: ENOENT: no such file or directory, open '/home/marco/.config/Cerebro/config.json'
    at Object.fs.openSync (fs.js:558:18)
    at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:173:20)
    at Object.fs.writeFileSync (fs.js:1233:33)
    at Object.get (/tmp/.mount_nnFS67/usr/bin/resources/app.asar/main.js:162:18)
    at Object.module.exports.Object.defineProperty.value (/tmp/.mount_nnFS67/usr/bin/resources/app.asar/main.js:642:24)
    at __webpack_require__ (/tmp/.mount_nnFS67/usr/bin/resources/app.asar/main.js:21:30)
    at /tmp/.mount_nnFS67/usr/bin/resources/app.asar/main.js:64:18
    at Object.<anonymous> (/tmp/.mount_nnFS67/usr/bin/resources/app.asar/main.js:67:10)
    at Object.<anonymous> (/tmp/.mount_nnFS67/usr/bin/resources/app.asar/main.js:3738:3)
    at Module._compile (module.js:571:32)

(cerebro:56588): Pango-ERROR **: 14:53:06.510: Harfbuzz version too old (1.3.1)

[1]    56588 trace trap (core dumped)  ./cerebro-0.3.2-x86_64\(1\).AppImage


I’m trying to run cerebro from the App Image, but it didn’t start from the shortcut then I tryed to run it from CLI and got the error above, looked around the internet and it seems that one package inside the image is not compatible with my system and it should be updated by the devs… Is it correct? Is this a known issue? Is there any workaround? Are there plans to support my distro? Thanks for taking the time to read this.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:18
  • Comments:12 (1 by maintainers)

github_iconTop GitHub Comments

leoroccocommented, Jul 14, 2020

Ubuntu 20.04. Same problem.

ThePrincellecommented, Sep 6, 2020

Exactly the same issue on my side, can’t believe that this hasn’t been fixed yet.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Pango-ERROR: Harfbuzz version too old · Issue #20348
The only solution is to ask the developers to update to the latest version of electron, that's all. 5
Read more >
Electron Versioning
Older lines will not be supported by the Electron project, ... At the same time, locking to a fixed version is dangerous because...
Read more >
electron-releases - npm
Complete and up-to-date info about every release of Electron. Latest version: 3.1171.0, last published: 2 months ago.
Read more >
Electron |
The Chromium version of Electron is usually bumped within one or two weeks after a new stable Chromium version gets released. This estimate...
Read more >
Unexpected token '?' when creating new app using electron ...
3. Seems like your node version is too old. – Konrad. Nov 24 at 8:48 · 1. You need to update your node...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found