Github messages for voidlinux
 help / color / mirror / Atom feed
From: Borys64 <Borys64@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] VSCode: (code-oss:28525): Pango-ERROR **: 13:19:31.389: Harfbuzz version too old (1.4.2)
Date: Wed, 28 Oct 2020 21:52:32 +0100	[thread overview]
Message-ID: <20201028205232.fnNRX_t4vc0Byf38xFC47AHDJ32s-gH782tRX9rAHvc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25934@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 995 bytes --]

Closed issue by Borys64 on void-packages repository

https://github.com/void-linux/void-packages/issues/25934

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### 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. 
```BASH
$ 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.


      parent reply	other threads:[~2020-10-28 20:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 13:25 [ISSUE] " Borys64
2020-10-28 13:31 ` Borys64
2020-10-28 13:57 ` ericonr
2020-10-28 13:57 ` ericonr
2020-10-28 14:00 ` ericonr
2020-10-28 20:52 ` Borys64
2020-10-28 20:52 ` Borys64 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201028205232.fnNRX_t4vc0Byf38xFC47AHDJ32s-gH782tRX9rAHvc@z \
    --to=borys64@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).