From: Luis Felipe via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: "45901@debbugs.gnu.org" <45901@debbugs.gnu.org>
Subject: bug#45901: GNOME Fonts takes about 20 seconds to display fonts
Date: Sat, 16 Jan 2021 15:24:00 +0000 [thread overview]
Message-ID: <Z5QftIVBbQM-HzIcPelxtwBs7ZhbjdWvtwad1yumzDLVd10Rngxaxi_QfnC3LMHksUxnTqGUIx3dH-yjvqhuZZSIvgaqUc4P6AMTyDUw3VU=@protonmail.com> (raw)
In-Reply-To: <87y2gt870d.fsf@cbaines.net>
On Saturday, January 16, 2021 11:18 AM, Christopher Baines <mail@cbaines.net> wrote:
> Hey,
>
> I've just pushed the fix I worked on for thumbnails [1].
>
> 1: https://git.savannah.gnu.org/cgit/guix.git/commit/?id=540893a8ccef41436a1c00ae268f74219f9ab220
>
> Could you guix pull, guix upgrade gnome-font-viewer, remove
> ~/.cache/thumbnails/fail/ and then re-test?
I just upgraded and thumbnails seem to be mostly fixed. That is, most of the thumbnails are displayed correctly. Some fonts have no thumbnail at all (Noto fonts like Noto Sans Armenian, Noto Sans Batak, Noto Sans Bengali, ...). And Source Han fonts have a placeholder icon (a blue, lowercase "a" in a white sheet).
The slowness issue seems to be a bug in GNOME Fonts (https://gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues/30).
What should we do with this bug report? Close it or leave it open until it is fixed upstream (I'd prefer the latter)?
next prev parent reply other threads:[~2021-01-16 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 18:54 bug#45901: GNOME Fonts takes about 20 seconds to display fonts Luis Felipe via Bug reports for GNU Guix
2021-01-16 11:18 ` Christopher Baines
2021-01-16 15:24 ` Luis Felipe via Bug reports for GNU Guix [this message]
2021-01-16 15:52 ` Christopher Baines
2021-01-16 16:28 ` Luis Felipe via Bug reports for GNU Guix
2021-12-23 23:39 ` Luis Felipe via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='Z5QftIVBbQM-HzIcPelxtwBs7ZhbjdWvtwad1yumzDLVd10Rngxaxi_QfnC3LMHksUxnTqGUIx3dH-yjvqhuZZSIvgaqUc4P6AMTyDUw3VU=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=45901@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).