From: vincele <vincele@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Intermittent bug in Firefox 88+ on x64/musl
Date: Thu, 10 Aug 2023 00:11:15 +0200 [thread overview]
Message-ID: <20230809221115.XPIaNjPJHd255dOout3HKCkamOmZ26WmEoSvS5C4lwA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31933@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
New comment by vincele on void-packages repository
https://github.com/void-linux/void-packages/issues/31933#issuecomment-1672229759
Comment:
@casualtyface, I see at least 2 different proposed workarounds in the few messages above (wayland & glibc chroot).
The problem with workarounds (that work) is that you then will not pursue proper bug fixing.
BTW, I can tell that I have not met that bug since using the glibc chroot, not even once. And there were a few firefox & other updates since Apr 9.
prev parent reply other threads:[~2023-08-09 22:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 2:28 [ISSUE] " thamesynne
2021-07-13 13:30 ` ericonr
2021-07-22 19:16 ` dkwo
2021-07-22 19:21 ` dkwo
2021-07-22 20:14 ` thamesynne
2021-07-22 20:15 ` thamesynne
2021-07-23 8:59 ` dkwo
2022-05-25 2:15 ` github-actions
2022-06-09 2:11 ` [ISSUE] [CLOSED] " github-actions
2023-04-08 8:31 ` vincele
2023-04-08 8:35 ` vincele
2023-04-08 8:39 ` vincele
2023-04-08 8:41 ` vincele
2023-04-08 13:31 ` dkwo
2023-04-08 14:14 ` vincele
2023-04-08 17:41 ` vincele
2023-04-08 18:02 ` snark-attack
2023-04-09 8:02 ` vincele
2023-08-09 21:05 ` casualtyface
2023-08-09 22:11 ` vincele [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=20230809221115.XPIaNjPJHd255dOout3HKCkamOmZ26WmEoSvS5C4lwA@z \
--to=vincele@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).