Skip to content
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

Segmentation fault with Libpurple right after beginning sync #330

Open
emassey0135 opened this issue Mar 13, 2023 · 0 comments
Open

Segmentation fault with Libpurple right after beginning sync #330

emassey0135 opened this issue Mar 13, 2023 · 0 comments

Comments

@emassey0135
Copy link

Hello,

I am trying to install Matrix Bifrost on a Raspberry Pi running Arch Linux ARM, with Synapse 1.74.0 and Synapse and Postgresql running on the same server as the bridge. I ran "yarn install" then "yarn build", customized the configuration file, and generated the registration file and added it to the Synapse configuration file. Line 3 of start.sh sets LD_PRELOAD to ./node_modules/node-purple/deps/libpurple/libpurple.so, but this file does not exist, so I commented out this line and uncommented line 4, which sets it to /usr/lib/libpurple.so.0, which on my system was Libpurple 2.14.12. When I ran this script, it failed with a segmentation fault right after printing "[RoomSync] Beginning sync". When I run Node.js in GDB starting the program with LD_PRELOAD and running the bridge directly without NPM, it says the segmentation fault is in the remove_timeout function in module.node from node-purple. I tried this with both Node 18 and Node 16 with the same result; the dependencies fail to install with Node 19. I also managed to compile Libpurple 2.13.0 using an old PKGBUILD, but the program still fails with a segmentation fault in the same function. I also tried it on my X86_64 laptop running Arch Linux with the same result. The bridge successfully starts the Purple instance and enumerates supported protocols.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant