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.

[SOLVED] Text and objects not displaying at inbox.google.com on Arch Linux

  • 4 replies
  • 6 have this problem
  • 28 views
  • Last reply by wrkerr

wrkerr
wrkerr
more options

Kind of an odd issue here in Firefox 40.0.2 on Arch Linux. It's not happening 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 safe mode, 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. My graphics system is the Intel GMA X4500HD, and I'm using the standard current 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).

Kind of an odd issue here in Firefox 40.0.2 on Arch Linux. It's not happening 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 safe mode, 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. My graphics system is the Intel GMA X4500HD, and I'm using the standard current 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).
Attached screenshots

Modified by wrkerr

Chosen solution

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.

Read this answer in context 👍 1

All Replies (4)

wrkerr
wrkerr Question owner
more options

<comment removed>

Modified by wrkerr

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You can check for problems with preferences.

Delete possible user.js and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.

Clear the cache and remove cookies only from websites that cause problems.

"Clear the Cache":

  • Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"

"Remove Cookies" from sites causing problems:

  • Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"

You can remove all data stored in Firefox from a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History > Show All History" or "View > Sidebar > History") or via the about:permissions page.

Using "Forget About This Site" will remove all data stored in Firefox from that domain like bookmarks, cookies, passwords, cache, history, and exceptions, so be cautious. If you have a password or other data from that domain that you do not want to lose then make sure to backup this data or make a note.

You can't recover from this 'forget' unless you have a backup of the involved files.

If you revisit a 'forgotten' website then data from that website will be saved once again.

wrkerr
wrkerr Question owner
more options

Thanks for the response cor-el. I attempted the steps you outlined, and it did not fix the problem. I even used the "Refresh Firefox" feature, and still same display.

Any other suggestions?

wrkerr
wrkerr Question owner
more options

Chosen Solution

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.