public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox crashes on some www-pages on a newer Gentoo system
Date: Thu, 2 Aug 2018 10:16:56 +1000	[thread overview]
Message-ID: <CAC=wYCFs_JYSJVYG8aEH_FV8frzsAi0mqopdjUdgJ+fEJUNGxQ@mail.gmail.com> (raw)
In-Reply-To: <CA+t6X7cuJ9sZ1uwTSssQ2MA=oCQtGregm9aLRC48pb3fnvoA7A@mail.gmail.com>

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

>
> > I would do something like 'emerge -1 xorg-server xorg-drivers
> > @x11-module-rebuild mesa llvm clang' then restart X and try again.
>
> Thank you for your reply.
>
> Initially, I understood the above recomendation as the suggestion to
> rebuild the packages mentioned above with different use flags.
>
> Do you think that rebuilding them with the same use flags may help?
>

It can, for example, if the major version of the kernel has changed but you
havent rebuild xorg since (I only recall having this issue once).

If you use newuse and changed-deps with emerge its probably less likely to
find other issues.


> The said problem appeared just since the intallation of the new
> Gentoo system in January-February 2018 and not since changing
> the major version of gcc this spring.
>
> P.S. clang is not installed on my Gentoo system at all.
>
>
I've checked the dependencies on my system, and firefox is pulling that in
for me, but checking the ebuilds you can see it becomes a dependency from
v60 onwards;

/usr/portage/www-client/firefox $ ls
files/               firefox-52.9.0.ebuild   Manifest
firefox-52.6.0.ebuild  firefox-60.1.0.ebuild   metadata.xml
firefox-52.8.0.ebuild  firefox-61.0-r1.ebuild
/usr/portage/www-client/firefox $ grep clang *
grep: files: Is a directory
firefox-60.1.0.ebuild:    >=sys-devel/clang-4.0.1
firefox-60.1.0.ebuild:    has_version "sys-devel/clang:${LLVM_SLOT}"
firefox-61.0-r1.ebuild:    >=sys-devel/clang-4.0.1
firefox-61.0-r1.ebuild:    has_version "sys-devel/clang:${LLVM_SLOT}"
/usr/portage/www-client/firefox $

[-- Attachment #2: Type: text/html, Size: 2368 bytes --]

  reply	other threads:[~2018-08-02  0:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27  8:16 [gentoo-user] Firefox crashes on some www-pages on a newer Gentoo system gevisz
2018-07-27  9:44 ` Mick
2018-07-27 10:44   ` gevisz
2018-07-27 10:57     ` Mick
2018-07-27 11:13       ` gevisz
2018-07-27 12:44         ` gevisz
2018-07-27 13:00           ` gevisz
2018-07-27 15:29             ` Mick
2018-07-27 18:49               ` gevisz
2018-07-27 20:02                 ` Mick
2018-07-28 12:24                   ` gevisz
2018-07-29 20:48                     ` gevisz
2018-07-31 23:41                       ` Adam Carter
2018-08-01  9:33                         ` gevisz
2018-08-02  0:16                           ` Adam Carter [this message]
2018-08-02  5:15                             ` gevisz
2018-09-07 15:32               ` gevisz
2018-09-07 16:05                 ` Mick
2018-09-16  7:19                   ` gevisz
2018-09-16  7:50                     ` Mick
2018-09-16  8:08                       ` Dale
2018-09-16 11:32                         ` gevisz
2018-09-16 11:47                           ` Mick
2018-09-16 11:51                           ` Dale
2018-09-16 11:25                       ` 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='CAC=wYCFs_JYSJVYG8aEH_FV8frzsAi0mqopdjUdgJ+fEJUNGxQ@mail.gmail.com' \
    --to=adamcarter3@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