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

VSCode: (code-oss:28525): Pango-ERROR **: 13:19:31.389: Harfbuzz version too old (1.4.2) #25934

Closed
Borys64 opened this issue Oct 28, 2020 · 4 comments

Comments

@Borys64
Copy link

Borys64 commented Oct 28, 2020

System

  • xuname:
    Void 5.8.16_1 i686 GenuineIntel notuptodate rrFFF
  • package:
    vscode-1.21.0_1

Expected behavior

Starting a session of Visual Studio Code

Actual behavior

The editor no longer opens after a full system upgrade. I have harfbuzz and pango installed and updated to the latest versions available - to no avail. I have also tried removing the package completely and reinstalling it multiple times.

$ code-oss --verbose
node[28515]: pthread_create: Invalid argument
(code-oss:28525): Pango-ERROR **: 13:19:31.389: Harfbuzz version too old (1.4.2)

Steps to reproduce the behavior

Use vscode-1.21.0_1 on i686 architecture.

@Borys64
Copy link
Author

Borys64 commented Oct 28, 2020

Same issue occurs when atom-1.26.1_1 is used. I've also tried to reinstall pango and harfbuzz, but they're a prerequisites of gtk+3 which might put the system at risk of breakage.

@ericonr
Copy link
Member

ericonr commented Oct 28, 2020

Hmm, you're probably out of luck. The vscode template has been moved to using system electron and it's on version 1.50.1, but it's broken for 32bit platforms. You can try to build it locally by removing the broken line, but I don't know what will happen. Since it's broken, you didn't get any updates.

I would recommend trying to download it from their official website, perhaps. Chances are it might be broken there as well.

@ericonr
Copy link
Member

ericonr commented Oct 28, 2020

Either way, you could try updating the system as well. One of the notuptodate packages might be relevant.

@Borys64
Copy link
Author

Borys64 commented Oct 28, 2020

Okay, thank you for your help, I'll look into building it myself.

@Borys64 Borys64 closed this as completed Oct 28, 2020
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

2 participants