Github messages for voidlinux
 help / color / mirror / Atom feed
From: Oreo639 <Oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Firefox rendering issues since 89.0 update
Date: Sat, 05 Jun 2021 11:13:24 +0200	[thread overview]
Message-ID: <20210605091324.aogq_cx51_0iA04DGs7H94caZ_p9XqYjR-EPo0M0ssE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31294@inbox.vuxu.org>

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

New comment by Oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/31294#issuecomment-855209695

Comment:
What is the output of `xbps-query -Rs xorg-fonts`?
Hasn't this been an issue for a long while?
(Make sure your remove xorg-fonts and all of it's dependencies the issue should go away)

Heck, this section was added to the void handbook specifically because of this issue:
https://docs.voidlinux.org/config/graphical-session/fonts.html?highlight=70-no-bitmaps.conf#fonts

  parent reply	other threads:[~2021-06-05  9:13 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05  5:35 [ISSUE] " Gottox
2021-06-05  5:43 ` Gottox
2021-06-05  8:14 ` lonwillett
2021-06-05  8:27 ` egorenar
2021-06-05  8:41 ` marmeladema
2021-06-05  9:05 ` Oreo639
2021-06-05  9:06 ` Oreo639
2021-06-05  9:07 ` Oreo639
2021-06-05  9:07 ` Oreo639
2021-06-05  9:08 ` Oreo639
2021-06-05  9:09 ` Oreo639
2021-06-05  9:13 ` Oreo639 [this message]
2021-06-05  9:13 ` Oreo639
2021-06-05  9:14 ` Oreo639
2021-06-05  9:14 ` Oreo639
2021-06-05  9:15 ` Oreo639
2021-06-05  9:19 ` Gottox
2021-06-05  9:21 ` Gottox
2021-06-05  9:27 ` Gottox
2021-06-05  9:29 ` Cnoob41
2021-06-05  9:30 ` lonwillett
2021-06-05  9:39 ` egorenar
2021-06-05  9:48 ` Oreo639
2021-06-05  9:49 ` Oreo639
2021-06-05 10:24 ` Oreo639
2021-06-05 11:54 ` Gottox
2021-06-07  2:07 ` hervyqa
2021-06-09 23:08 ` stnby
2021-06-09 23:24 ` Duncaen
2021-06-10 19:01 ` PurpleVsGreen
2021-06-11 22:38 ` stnby
2021-06-15  3:33 ` arp242
2021-06-15  3:34 ` arp242
2021-06-16  9:37 ` Unixware
2021-06-16 10:32 ` Duncaen
2021-06-16 10:36 ` Unixware
2021-06-20 17:29 ` Oreo639
2021-06-20 19:48 ` HadetTheUndying
2021-06-20 19:52 ` Duncaen
2021-06-20 21:29 ` Oreo639
2021-06-20 21:29 ` Oreo639
2021-06-21 15:52 ` mtbc
2021-07-15 11:51 ` ahesford
2021-08-02 12:43 ` stnby
2021-08-02 13:44 ` [ISSUE] [CLOSED] " ahesford
2023-04-15 11:51 ` Anachron
2023-04-15 11:52 ` Anachron
2023-07-15 15:56 ` StreetStrider

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=20210605091324.aogq_cx51_0iA04DGs7H94caZ_p9XqYjR-EPo0M0ssE@z \
    --to=oreo639@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).