cerebroapp/cerebro

fix: segmentation fault on start

piegamesde opened this issue · 12 comments

  • I am on the latest Cerebro.app version

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

  • OS version and name: Arch Linux

  • Cerebro.app version: 0.3.2

Issue

When I start cerebro, it crashes:

installed: X-AppImage-BuildId=847a0770-d98f-11a7-0ebd-e5b83ffea09e image: X-AppImage-BuildId=847a0770-d98f-11a7-0ebd-e5b83ffea09e
Failed to get crash dump id.
Report Id: 
[1]    3603 segmentation fault (core dumped)  ./cerebro-0.3.2-x86_64.AppImage

I get the same error when running the AUR packages.

similar situation, also Arch

Same to me on Arch.
I also cannot install by source because nodobjc package fails to build.

Same to me on Arch.
When I try to start cerebro in the console as follow:

cerebro --help
cerebro -h

it starts after few retries and it works as expected, but the context menu is not readable.
image

Maybe some unicode issues?

Same to me (Arch), mine won't event initialize config file

Since there's no launcher satisfying my needs, I started my own.
Take a look:
https://github.com/vonal-project

It's still useless, there're no plugins, cannot be configured by files. But it is actively developed!

I managed to make it work on manjaro 18.04 by compiling from sources (version 0.3.1), I followed instruction on README.md but i before each yarn I run yarn upgrade.

(node version 8.16 AUR node-lts-carbon)

I switched to ulauncher. Seems to be a good launcher too.

Same problem here on Arch Linux. In the AUR version, it asks for nodejs-lts-carbon and I use a newer nodejs.

$ yay -S cerebro
:: There are 2 providers available for cerebro:
:: Repository AUR
    1) cerebro 2) cerebro-git 

Enter a number (default=1): 1
 -> Could not find all required packages:
        nodejs-lts-carbon (Wanted by: cerebro)

I have the same issue on kali linux

I have the same issue on endeavour os

I'm closing this issue as outdated. We recently released v0.8.0 which has a lot of dependency updates and bug fixes. Try it and, if the problem persists, we can open a new issue.