This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

layers.acceleration.force-enabled = true & layers.force-active = true seem to solve my screen tearing and graphical glitches on Ubuntu 18.04...any risks?

  • 4 replies
  • 1 has this problem
  • 839 views
  • Last reply by magma1988

magma1988
magma1988
more options

I had screen tearing and graphical glitches when browsing. [layers.acceleration.force-enabled = true] solved screen tearing, but I still had some graphical glitches from time to time which now seem to have been fixed with [layers.force-active = true].

Could this be a working configuration on the long term? Currently it is running like a charm...

I'm running Ubuntu 18.04 and had already turned off hardware acceleration and smooth scrolling without the desired results before trying the above-mentioned things. I also played around with the xorg.config.d settings of the OS...

Best regards Mike

I had screen tearing and graphical glitches when browsing. [layers.acceleration.force-enabled = true] solved screen tearing, but I still had some graphical glitches from time to time which now seem to have been fixed with [layers.force-active = true]. Could this be a working configuration on the long term? Currently it is running like a charm... I'm running Ubuntu 18.04 and had already turned off hardware acceleration and smooth scrolling without the desired results before trying the above-mentioned things. I also played around with the xorg.config.d settings of the OS... Best regards Mike

Chosen solution

Basically you are just forcing Hardware acceleration to run. The only risk is that it could break in the future, but then you'd just disable it. I'd suggest keeping your graphics drivers up to date along with Firefox, but otherwise it'll be fine (hopefully)

Read this answer in context 👍 1

All Replies (4)

user633449
user633449
more options

Chosen Solution

Basically you are just forcing Hardware acceleration to run. The only risk is that it could break in the future, but then you'd just disable it. I'd suggest keeping your graphics drivers up to date along with Firefox, but otherwise it'll be fine (hopefully)

magma1988
magma1988 Question owner
more options

Thank you Tyler for your reply!

Found a better solution. Setting gfx.xrender.enabled=true and layers.acceleration.force-enabled & layers.force-active back to default solves everything.

dsfounis
dsfounis
more options

magma1988 said

Thank you Tyler for your reply! Found a better solution. Setting gfx.xrender.enabled=true and layers.acceleration.force-enabled & layers.force-active back to default solves everything.

How do you believe this is better than forcing hardware acceleration?

I'm on Ubuntu 18.04.1, Firefox 64.0 and I'm going through the same problems as you.

My AskUbuntu stack question: https://askubuntu.com/questions/1102427/strange-ghost-images-transparency-effect-in-full-screen-videos/1103067#1103067

magma1988
magma1988 Question owner
more options

With layers.acceleration.force-enabled=true you get a very smooth scrolling experience, but sometimes graphical glitches and artifacts happen - e.g. on the Ubuntu Certified Hardware website when hovering over the different manufacturers. Setting layers.force-active= true will solve this issue. In terms of performance this wasn't really good. Seemed to slow down everything. Setting both to default again and gfx.xrender.enabled=true will make everything feel snappier and faster again without graphical issues and tearing. This is why I believe it to be a better solution...just my opinion. I'm still doing it that way. Hope it helps...