Arch Linux

wrkerr

Member

Registered: 2015-04-02

Posts: 18

[SOLVED]Text and objects not displaying in Firefox at inbox.google.com

Kind of an odd issue here. It's not happening on any other distros, or in any other browsers, but in Firefox the page inbox.google.com is not displaying properly---all the text and visual objects are missing, and only the background is displayed. The site works fine in Chromium, and I've tried disabling all my Firefox extensions, and it continues to happen every time I visit the page in Firefox. No other sites seem to be affected. I'm running an up-to-date Arch install, with the standard Firefox from the repo, in Gnome 3.16.2 from the repo. My graphics system is the Intel GMA X4500HD, and I'm using the standard Intel driver in the repo. Has anyone else seen anything like this? (my email address is blanked out by me... everything else is untouched in screenshot)
http://s21.postimg.org/ecajete53/inbox.jpg

Mod note: Converted img to url. See https://wiki.archlinux.org/index.php/Fo … s_and_code for image posting guidelines -- WorMzy

Last edited by wrkerr (2015-09-08 13:50:07)

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: [SOLVED]Text and objects not displaying in Firefox at inbox.google.com

Do not post full screen pictures; use thumbnails instead.
https://wiki.archlinux.org/index.php/Fo … s_and_code

wrkerr

Member

Registered: 2015-04-02

Posts: 18

Re: [SOLVED]Text and objects not displaying in Firefox at inbox.google.com

Thank you for fixing that, and for educating me. Sorry!

wrkerr

Member

Registered: 2015-04-02

Posts: 18

Re: [SOLVED]Text and objects not displaying in Firefox at inbox.google.com

Here's a thumbnail version.

I've tried everything I can think of without success.

wrkerr

Member

Registered: 2015-04-02

Posts: 18

Re: [SOLVED]Text and objects not displaying in Firefox at inbox.google.com

Still not sure what caused this, but for the sake of documentation... When I enabled OpenGL Off-Main-Thread Compositing (OMTC) in about:config of Firefox, the problem went away. Must have been something to do with rendering.