From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 60839@debbugs.gnu.org
Cc: jgart@dismail.de
Subject: [bug#60839] [PATCH] gnu: qutebrowser: Add note to description about font rendering bug.
Date: Sat, 01 Jul 2023 10:13:23 +0200 [thread overview]
Message-ID: <87a5wgkq1o.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20230115220211.4022-1-jgart@dismail.de> (jgart via Guix-patches via's message of "Sun, 15 Jan 2023 16:02:12 -0600")
Hello,
jgart via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/web-browsers.scm (qutebrowser): Add note.
> [description]: Add note about font rendering bug.
>
> Hi, this patch adds a note about how to get fonts to render when you first install qutebrowser.
> ---
> gnu/packages/web-browsers.scm | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/web-browsers.scm b/gnu/packages/web-browsers.scm
> index a126902395..9903f1f4aa 100644
> --- a/gnu/packages/web-browsers.scm
> +++ b/gnu/packages/web-browsers.scm
> @@ -548,7 +548,11 @@ (define-public qutebrowser
> (home-page "https://qutebrowser.org/")
> (synopsis "Minimal, keyboard-focused, vim-like web browser")
> (description "qutebrowser is a keyboard-focused browser with a minimal
> -GUI. It is based on PyQt5 and QtWebEngine.")
> +GUI. It is based on PyQt5 and QtWebEngine. Due to a
> +@url{https://bugs.chromium.org/p/chromium/issues/detail?id=1164975,
> +known bug} in qtwebengine, add @code{c.qt.args =
> +['disable-seccomp-filter-sandbox']} to your @file{config.py} in order
> +to allow fonts to render properly.")
Following this link, it seems the bug was fixed a few weeks ago. WDYT?
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2023-07-01 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 22:02 [bug#60839] [PATCH] gnu: qutebrowser: Add note to description about font rendering bug jgart via Guix-patches via
2023-07-01 8:13 ` Nicolas Goaziou [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=87a5wgkq1o.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=60839@debbugs.gnu.org \
--cc=jgart@dismail.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.