From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Firefox 72 segfaults
Date: Fri, 14 Feb 2020 09:34:00 +0100 [thread overview]
Message-ID: <20200214083400.I7xPddZJKmOvGtbsbPYM6mPrLfxw_DhHEWwoaYfgAU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18179@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
Closed issue by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/18179
Description:
### System
* xuname:
Void 5.4.10_1 x86_64 GenuineIntel notuptodate rrrmDFFFFF
* package:
firefox-72.0.1_1
### Expected behavior
Firefox to launch
### Actual behavior
Crashes instantly with "Speicherzugriffsfehler" (segfault)
### Steps to reproduce the behavior
Launch firefox
### STRACE
https://gist.github.com/Anachron/cd8c7a05b2eaa1a36cc866f15e46a958
prev parent reply other threads:[~2020-02-14 8:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 13:36 [ISSUE] " voidlinux-github
2020-01-10 14:16 ` voidlinux-github
2020-01-10 14:18 ` voidlinux-github
2020-01-10 15:45 ` voidlinux-github
2020-01-11 12:06 ` voidlinux-github
2020-01-13 15:33 ` voidlinux-github
2020-01-14 16:07 ` voidlinux-github
2020-01-14 18:23 ` voidlinux-github
2020-01-14 19:10 ` voidlinux-github
2020-01-14 19:15 ` voidlinux-github
2020-01-14 19:16 ` voidlinux-github
2020-01-14 19:17 ` voidlinux-github
2020-01-14 19:17 ` voidlinux-github
2020-01-14 19:18 ` voidlinux-github
2020-01-14 19:20 ` voidlinux-github
2020-01-14 19:22 ` voidlinux-github
2020-01-14 19:23 ` voidlinux-github
2020-01-14 20:00 ` voidlinux-github
2020-01-14 20:20 ` voidlinux-github
2020-01-14 20:36 ` voidlinux-github
2020-01-14 20:55 ` voidlinux-github
2020-01-14 20:55 ` voidlinux-github
2020-01-14 20:59 ` voidlinux-github
2020-01-14 21:08 ` voidlinux-github
2020-01-14 21:46 ` voidlinux-github
2020-01-14 23:52 ` voidlinux-github
2020-02-14 8:34 ` voidlinux-github
2020-02-14 8:34 ` voidlinux-github [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=20200214083400.I7xPddZJKmOvGtbsbPYM6mPrLfxw_DhHEWwoaYfgAU4@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).