X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Vertical colored bars on left side of window?

Kuphostiwe

Arch Linux, 64-bit

Radeon HD 7750 w/ Mesa 10.6.4

Gnome 3.16.2

Firefox 40.0.2 (problem does not occur on FF 39.0.3)


Any Firefox window has a colored vertical region (20-or-so pixels wide) beginning just under the system title bar and extending down to the bottom of the FF window. The region begins as a single color(1) but then, as the viewport changes(2) this region is segmented into sub-regions of independently varying colors. Multiple windows maintain their own independent colored region.

If multiple firefox windows are opened, each has its own region. Context menus (e.g. right clicking anywhere in the FF window) also have such a region. Disabling all extensions, plugins, and themes has no effect.

(1) The colors I've observed are always fundamental (cyan, magenta, yellow, green, blue, red, gray). When the color is set or changed (described below) the color seems to be set at random - that is to say I cannot distinguish a pattern as to how

(2) Scrolling the viewport or invoking a browser modal/prompt/file dialog will cause the entire region to change to one other color. Certain (I can't nail down the rhyme or reason) block-level changes to a page will cause a sub-region to appear, horizontally aligned with said block. Page-wide changes "reset" these sub regions. Animations on the page causing color changes (such as the fading in of a modal overlay div or the slow sliding up of the Firefox address bar when entering fullscreen) will cause rapid color change during the period of animation/transition. Blurring the Firefox window or using the PrintScreen button will also reset the entire region back to one color so I'm unable to get a screengrab of varying subregions.


Is this a problem with Firefox? Where should I file a bug report? Mozilla? Gnome? X? Mesa?

Arch Linux, 64-bit Radeon HD 7750 w/ Mesa 10.6.4 Gnome 3.16.2 Firefox 40.0.2 (problem does not occur on FF 39.0.3) ---------------- Any Firefox window has a colored vertical region (20-or-so pixels wide) beginning just under the system title bar and extending down to the bottom of the FF window. The region begins as a single color(1) but then, as the viewport changes(2) this region is segmented into sub-regions of independently varying colors. Multiple windows maintain their own independent colored region. If multiple firefox windows are opened, each has its own region. Context menus (e.g. right clicking anywhere in the FF window) also have such a region. Disabling all extensions, plugins, and themes has no effect. (1) The colors I've observed are always fundamental (cyan, magenta, yellow, green, blue, red, gray). When the color is set or changed (described below) the color seems to be set at random - that is to say I cannot distinguish a pattern as to how (2) Scrolling the viewport or invoking a browser modal/prompt/file dialog will cause the entire region to change to one other color. Certain (I can't nail down the rhyme or reason) block-level changes to a page will cause a sub-region to appear, horizontally aligned with said block. Page-wide changes "reset" these sub regions. Animations on the page causing color changes (such as the fading in of a modal overlay div or the slow sliding up of the Firefox address bar when entering fullscreen) will cause rapid color change during the period of animation/transition. Blurring the Firefox window or using the PrintScreen button will also reset the entire region back to one color so I'm unable to get a screengrab of varying subregions. ----------------- Is this a problem with Firefox? Where should I file a bug report? Mozilla? Gnome? X? Mesa?
Ama-screenshot ananyekiwe

Okulungisiwe ngu Chris Tonkinson

Isisombululo esikhethiwe

Just wanted to post an update. I once again revisited this issue to try to figure out what the problem was (this time with v44.0).

Again, no change of settings resolved the issue, nor did disabling extensions and themes.

However, this time, a newly created profile did not show the behavior. To this new profile I installed all of my extensions and themes, configured my custom settings, and I have not seen the problem return for days now.

Not sure what happened here. The update from v39 to v40 (with no other changes) introduced this strange artifact, which at first was not solvable with a new profile, but now is. I'm at a loss.

Funda le mpendulo ngokuhambisana nalesi sihloko 0

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • This plugin provides integration with Gnome Shell for live extension enabling and disabling. It can be used only by extensions.gnome.org

Isisebenziso

  • Firefox 40.0.2
  • Umsebenzisi oyi-ejenti: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
  • I-URL Yokweseka: https://support.mozilla.org/1/firefox/40.0.2/Linux/en-US/

Izandiso

  • Adblock Edge 2.1.9.1-signed ({fe272bd1-5f76-4ea4-8501-a05d35d823fc})
  • Ghostery 5.4.6.1 (firefox@ghostery.com)
  • LastPass 3.2.16 (support@lastpass.com)
  • NoScript 2.6.9.36 ({73a6fe31-595d-460b-a920-fcc0f8843232})
  • Restartless Restart 9.1-signed (restartless.restart@erikvold.com)

I-Javascript

  • incrementalGCEnabled: True

Imidwebo

  • adapterDescription: X.Org -- Gallium 0.4 on AMD CAPE VERDE
  • adapterDeviceID: Gallium 0.4 on AMD CAPE VERDE
  • adapterDrivers:
  • adapterRAM:
  • adapterVendorID: X.Org
  • driverDate:
  • driverVersion: 3.0 Mesa 10.6.4
  • info: {u'AzureCanvasBackend': u'cairo', u'AzureFallbackCanvasBackend': u'none', u'AzureContentBackend': u'cairo', u'AzureSkiaAccelerated': 0}
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'']
  • numTotalWindows: 1
  • supportsHardwareH264: False
  • webglRenderer: X.Org -- Gallium 0.4 on AMD CAPE VERDE
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Basic

Okuthandwayo Okulungisiwe

Misc

  • Umsebenzisi JS: Cha
  • Ukufinyeleleka: Cha
FredMcD
  • Top 10 Contributor
4257 izisombululo 59604 izimpendulo
Kuphostiwe

check this:

  • see if there are updates for your graphics drive drivers

https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

  • disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)

https://forums.adobe.com/message/4468493#TemporaryWorkaround

  • disable hardware acceleration in the Flash plugin

https://forums.adobe.com/thread/891337 See also:

check this: * see if there are updates for your graphics drive drivers '''https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration''' * disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later) '''https://forums.adobe.com/message/4468493#TemporaryWorkaround''' * disable hardware acceleration in the Flash plugin '''https://forums.adobe.com/thread/891337''' See also: * '''http://kb.mozillazine.org/Flash#Troubleshooting'''

Umnikazi wombuzo

Drivers are fully patched (again, this problem does *not* occur on FF 39.0.3) and Flash is disabled.

Drivers are fully patched (again, this problem does *not* occur on FF 39.0.3) and Flash is disabled.
FredMcD
  • Top 10 Contributor
4257 izisombululo 59604 izimpendulo
Kuphostiwe

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options)
key, and then starting Firefox. Is the problem still there?

Start '''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Firefox in Safe Mode]''' {web Link} by holding down the '''<Shift><br> ''(Mac Options)'' ''' key, and then starting Firefox. Is the problem still there?
cor-el
  • Top 10 Contributor
  • Moderator
17532 izisombululo 158526 izimpendulo
Kuphostiwe

Try to toggle the gfx.xrender.enabled pref on the about:config page.

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

Try to toggle the <b>gfx.xrender.enabled</b> pref on the <b>about:config</b> page. You can open the <b>about:config</b> page via the location/address bar. You can accept the warning and click "I'll be careful" to continue. *http://kb.mozillazine.org/about:config

Umnikazi wombuzo

@FredMcD Yes, the problem is still there. Again, "Disabling all extensions, plugins, and themes has no effect. " (and that includes safe mode)


@cor-el bad advice - that caused Firefox not to render anything other than the title bar. Completely blank white canvas. I had to edit prefs.js to reset this before the browser was usable again.

@FredMcD Yes, the problem is still there. Again, "Disabling all extensions, plugins, and themes has no effect. " (and that includes safe mode) ---- @cor-el bad advice - that caused Firefox not to render anything other than the title bar. Completely blank white canvas. I had to edit prefs.js to reset this before the browser was usable again.
guigs 1072 izisombululo 11697 izimpendulo
Kuphostiwe

You mentioned a prefs.js file. Are there any customization other than what has been mentioned?

You mentioned a prefs.js file. Are there any customization other than what has been mentioned?

Umnikazi wombuzo

@guigs - this problem persists in a clean new FF profile, in Safe Mode, so it's nothing to do with configuration.

I had a thought, and fired up Firefox Developer Edition (42.0a2, 2015-08-21) which does not exhibit this behavior.

@guigs - this problem persists in a clean new FF profile, in Safe Mode, so it's nothing to do with configuration. I had a thought, and fired up Firefox Developer Edition (42.0a2, 2015-08-21) which does not exhibit this behavior.

Umnikazi wombuzo

I think it's safe to assume this is a bug of some sort, as the most recent update was the only change made between a working state and this.

I'm less interested in troubleshooting and more interested in filing a bug report. Per my initial request, I'm just trying to figure out where to file.

I think it's safe to assume this is a bug of some sort, as the most recent update was the only change made between a working state and this. I'm less interested in troubleshooting and more interested in filing a bug report. Per my initial request, I'm just trying to figure out where to file.

Isisombululo Esikhethiwe

Just wanted to post an update. I once again revisited this issue to try to figure out what the problem was (this time with v44.0).

Again, no change of settings resolved the issue, nor did disabling extensions and themes.

However, this time, a newly created profile did not show the behavior. To this new profile I installed all of my extensions and themes, configured my custom settings, and I have not seen the problem return for days now.

Not sure what happened here. The update from v39 to v40 (with no other changes) introduced this strange artifact, which at first was not solvable with a new profile, but now is. I'm at a loss.

Just wanted to post an update. I once again revisited this issue to try to figure out what the problem was (this time with v44.0). Again, no change of settings resolved the issue, nor did disabling extensions and themes. However, this time, a newly created profile did not show the behavior. To this new profile I installed all of my extensions and themes, configured my custom settings, and I have not seen the problem return for days now. Not sure what happened here. The update from v39 to v40 (with no other changes) introduced this strange artifact, which at first was not solvable with a new profile, but now is. I'm at a loss.
FredMcD
  • Top 10 Contributor
4257 izisombululo 59604 izimpendulo
Kuphostiwe

All I will say is, Whatever works, works. That was very good work. Well Done.

All I will say is, Whatever works, works. That was very good work. Well Done.