From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Some symbols render incomplete in text mode
Date: Tue, 10 May 2022 18:42:33 +0300 [thread overview]
Message-ID: <CA+t6X7eLLaJhVOUwzLr+yqRo4iQoHSV6Q7r5-Zy3TiEDWVgcjA@mail.gmail.com> (raw)
In-Reply-To: <YnZAF0NzNnKd2fh1@kern>
сб, 7 мая 2022 г. в 12:47, Frank Steinmetzger <Warp_7@gmx.de>:
>
> Am Thu, May 05, 2022 at 08:46:39PM +0300 schrieb gevisz:
>
> > It seems to me that the problem is somehow related
> > to redrawing a frame. However, I am still not sure if
> > it is a problem of software or hardware.
> >
> > I have not tried another google-chrome profile so far.
>
> I would create a new (temporary test) user and log on with that. If the
> problem still persists, it’s either a system config, a library (cairo,
> freetype et al, graphics driver) or maybe even a hardware issue.
Yes. It is exactly how I intended to do this, and sorry for not having
done it yet.
However, I have found that the problem of the incomplete rendering
symbols in text mode appears only after I play youtube videos in
google-chrome and persist after exiting it.
Playing youtube videos in firefox-bin does not cause this problem to
appear, nor does running google-chrome without playing youtube videos
in it.
Moreover, in Firefox-bin, I even do not have the problem with
incomplete rendering symbols in the youtube video player toolbar.
So, I already can blame this problem completely on google-chrome.
Moreover, I already know how to avoid it. :)
P.S. My current version of google-chrome is 101.0.4951.54. However,
the problem already appeared in its earlier versions and has survived
several updates of the google-chrome.
next prev parent reply other threads:[~2022-05-10 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 20:57 [gentoo-user] Some symbols render incomplete in text mode gevisz
2022-04-27 10:55 ` Frank Steinmetzger
2022-04-28 18:20 ` gevisz
2022-04-28 18:23 ` gevisz
2022-04-28 21:41 ` Frank Steinmetzger
2022-04-30 11:49 ` gevisz
2022-05-01 10:57 ` Michael
2022-05-01 18:46 ` gevisz
2022-05-02 12:03 ` Michael
2022-05-02 19:54 ` gevisz
2022-05-05 17:46 ` gevisz
2022-05-07 9:47 ` Frank Steinmetzger
2022-05-10 15:42 ` gevisz [this message]
2022-05-20 9:13 ` gevisz
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=CA+t6X7eLLaJhVOUwzLr+yqRo4iQoHSV6Q7r5-Zy3TiEDWVgcjA@mail.gmail.com \
--to=gevisz@gmail.com \
--cc=gentoo-user@lists.gentoo.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