-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Symbol lookup error on linux #2015
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
Comments
I have the same error - not happening with canvas 2.9.0, but with canvas 2.9.1 canvas 2.9.1
I only had the issue if I called: |
@zbjornson - any ideas? - that might related to your last commits |
any update on this? |
FYI this is fixed in Ubuntu 22 LTS, the only affected version seems to be v20 |
I have the latest Ubuntu 22 LTS and this keeps happening, any idea how to fix? I'm on the latest 2.10.2. I had to revert back to 2.8.0 |
It worked for me |
I have been testing this. |
I stand corrected on the version of Ubuntu. I was previously testing on Ubuntu 20, and now I'm on Ubuntu 22.04.1. |
Any Update? |
Any update on this? I am getting this error when deployed on heroku, it only happens when calling canvas.registerFont(font.filePath, {family: font.family}) |
Uh oh!
There was an error while loading. Please reload this page.
Issue or Feature
Whenever I try to create a canvas my app crashes with the following message:
node: symbol lookup error: /app/node_modules/canvas/build/Release/canvas.node: undefined symbol: pango_fc_font_map_set_default_substitute
There is no error stack associated with this crash, this is all the info I get from it.
Steps to Reproduce
This is a TS code sample but it should be easily convertible to JS. It also requires an image of size 800x200 on a folder called assets with the name
joinBackground.png
. I, unfortunately, cannot debug this issue further than this function as I don't have access to a Linux machine and this only happens on the server where I host my app.Your Environment
npm list canvas
oryarn list canvas
): 2.9.1 (didn't happen in 2.9.0)The text was updated successfully, but these errors were encountered: