Github messages for voidlinux
 help / color / mirror / Atom feed
From: mtboehlke <mtboehlke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: firefox i686 segfaults on startup
Date: Fri, 30 Sep 2022 17:57:18 +0200	[thread overview]
Message-ID: <20220930155718.LoGt-SVymDfSwi5y5O_p7w1ScFlH3Hb6utuZ3Dfr9Vc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39538@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

New comment by mtboehlke on void-packages repository

https://github.com/void-linux/void-packages/issues/39538#issuecomment-1263704159

Comment:
So... I am one of those few still using an i686 device.  You know what they say, the cheapest laptop is the one you have.  Seeing this issue I upgraded and also am getting segmentation fault on attempting to start Firefox.  I can also say 104 worked for me and my processor does support SSE2.

  parent reply	other threads:[~2022-09-30 15:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  9:13 [ISSUE] " thamesynne
2022-09-30  9:35 ` thamesynne
2022-09-30 11:12 ` Duncaen
2022-09-30 11:25 ` thamesynne
2022-09-30 11:27 ` thamesynne
2022-09-30 11:37 ` q66
2022-09-30 12:19 ` thamesynne
2022-09-30 12:28 ` thamesynne
2022-09-30 13:03 ` q66
2022-09-30 13:15 ` thamesynne
2022-09-30 13:20 ` thamesynne
2022-09-30 13:44 ` q66
2022-09-30 13:59 ` thamesynne
2022-09-30 14:08 ` paper42
2022-09-30 14:29 ` q66
2022-09-30 15:15 ` mtboehlke
2022-09-30 15:16 ` q66
2022-09-30 15:17 ` q66
2022-09-30 15:57 ` mtboehlke [this message]
2022-09-30 21:36 ` [ISSUE] [CLOSED] " Duncaen

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=20220930155718.LoGt-SVymDfSwi5y5O_p7w1ScFlH3Hb6utuZ3Dfr9Vc@z \
    --to=mtboehlke@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).