Skip to content

[bug] core dump upon startup on Linux #2078

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bard opened this issue Jun 6, 2025 · 3 comments
Open

[bug] core dump upon startup on Linux #2078

bard opened this issue Jun 6, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@bard
Copy link

bard commented Jun 6, 2025

Describe the bug

$ ./Onlook-x86_64.AppImage

(process:477913): Gtk-ERROR **: 09:21:13.411: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported
Trace/breakpoint trap (core dumped)

Haven't investigated in depth but here's the same issue in logseq. It doesn't reference the fixing commit explicitly but looking at the date I think it's this one.

@bard bard added the bug Something isn't working label Jun 6, 2025
@Rish-it
Copy link
Contributor

Rish-it commented Jun 7, 2025

Hi @bard, thanks for the detailed bug report! Could you provide some additional info:

  • What Linux distribution are you using?
  • Which version of the Onlook AppImage did you download?
  • Can you share the output of ldd ./Onlook-x86_64.AppImage?

I'm investigating this GTK conflict issue and any additional details would help.

@bard
Copy link
Author

bard commented Jun 7, 2025

Hi @Rish-it, I'm using Arch. I downloaded the AppImage from https://onlook.com/download, I don't see a version number, md5sum below:

$ md5sum Onlook-x86_64.AppImage 
c006d34d6aa0656404f7a6314a5058a8  Onlook-x86_64.AppImage
$ ldd Onlook-x86_64.AppImage 
	not a dynamic executable

@Rish-it
Copy link
Contributor

Rish-it commented Jun 7, 2025

@bard Thanks for sharing the details this needs little more debugging. This is most likely the conflicting issue form GTK as you attached in the first shot

# Check for conflicting native modules
npm ls | grep -E "(gtk|cairo|pango|gdk)"

# Remove any old GTK-related native deps
npm uninstall any-gtk-related-packages

# Clean node_modules
rm -rf node_modules package-lock.json
npm install

I’d recommend getting rid of multiple GTK versions, and double-checking that your Electron version is compatible with the native modules you’re using. After that, try rebuilding.

Let me know how it goes — happy to help further if it’s still giving trouble!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants