SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Maybe check about:support to see if anything has changed? (There's too much info there, but you can copy the text-only versions from 87 & 88.x and diff to see if anything jumps out.)
Ooo, thanks for that. That was a great tip and revealed this gem. So you were definitely on the right track there.
Features
-Compositing: Basic
+Compositing: WebRender
So compositor has changed somehow between 87 and 88. And this is likely where the issues are coming from.
Now to work out what that means :-) Or as a worst-case, how to disable it.. gfx.webrender.all is still false.
It seems that the underlying issue with webrender on some Intel graphics chipsets is not new, however something has changed in 88 to use webrender in more contexts it seems.
Is this possibly something that was changed at the compile time on Slackware's side during the switch to 88.0?
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
I don't know if this is any help or not, but on 14.2, I just downloaded and am using 88.0.1 and don't see anything wrong anywhere. Could that mean that it's something in Slackware current that's not right and not in Firefox itself? I don't use Firefox anymore since they jumped on the bandwagon of trying to tell me I'm too white, so this was just a quick check to see if it was 'glitchy' on other versions of Slackware in the hopes that it may be of some use in helping. After this post using it (Firefox) it's getting uninstalled again, heh.
As a workaround for myself (and others on affected Intel chipsets), setting gfx.webrender.force-disabled to true and restarting returns to the Basic renderer.
I'm not sure if this is the most ideal workaround, but if there is an issue there that can't be fixed and isn't caused by a Slackware compile option, then I guess it is something I can live with :-)
It only returns me to where I was on 87.0, so that is bearable.
As a workaround for myself (and others on affected Intel chipsets), setting gfx.webrender.force-disabled to true and restarting returns to the Basic renderer.
I'm not sure if this is the most ideal workaround, but if there is an issue there that can't be fixed and isn't caused by a Slackware compile option, then I guess it is something I can live with :-)
It only returns me to where I was on 87.0, so that is bearable.
Just an update, this issue no longer seems present in Firefox 89.0 (and 89.0.2) so the workaround is no longer necessary and can/should likely be removed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.