unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: phodina <phodina@protonmail.com>
To: Christophe Pisteur <christophe.pisteur@fsfe.org>
Cc: help-guix@gnu.org
Subject: Re: Incorrect display of system fonts after guix system reconfigure (2021_10_29)
Date: Tue, 02 Nov 2021 21:47:57 +0000	[thread overview]
Message-ID: <xUywo34hYpR_UJiA9NDIb4YXm_iZ8MQeWu46NISTDfPT_U7F-gV8_C_Rn3EVe_v2VYVvflDgAdVirynE-qpi34TuokjkQidEeX_OqrGirp8=@protonmail.com> (raw)
In-Reply-To: <937d3634814fe67a1e580fe2c392067aa277cbc3.camel@fsfe.org>

Hi,

On Sunday, October 31st, 2021 at 10:00 PM, Christophe Pisteur <christophe.pisteur@fsfe.org> wrote:

> Le samedi 30 octobre 2021 à 13:06 +0000, phodina a écrit :
>
> > Hi Christophe,
> >
> > have you tried to run
> >
> > fc-cache -f
> >
> > to update the font cache to solve the issue?
> >
> > Petr
>
> Thank you very much. This solved the problem inside my session, but:- not in the gdm login screen, which still shows bold fonts without precise outline;- I don't understand why I had to do this action (fc-cache -f) when all other times, a 'sudo guix system reconfigure' worked out of the box. is this a bug?Christophe

You're welcome :-)

Looked around and found this long open issue regarding the font update [1].

Now to the gdm issue. I use sddm instead so I just checked some documentation.

Based on the Archwiki [2] I'd have a look at dconf. I will probably also be necessary to run manually dconf update.

1: http://issues.guix.gnu.org/18640

2: https://wiki.archlinux.org/title/GDM#dconf_configuration


      reply	other threads:[~2021-11-02 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 10:14 Incorrect display of system fonts after guix system reconfigure (2021_10_29) Christophe Pisteur
2021-10-30 13:06 ` phodina via
2021-10-31 21:00   ` Christophe Pisteur
2021-11-02 21:47     ` phodina [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

  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='xUywo34hYpR_UJiA9NDIb4YXm_iZ8MQeWu46NISTDfPT_U7F-gV8_C_Rn3EVe_v2VYVvflDgAdVirynE-qpi34TuokjkQidEeX_OqrGirp8=@protonmail.com' \
    --to=phodina@protonmail.com \
    --cc=christophe.pisteur@fsfe.org \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).