1238962 - The FXA settings are overlapping the Add account picture screen

Status: RESOLVED INCOMPLETE

(Core :: Graphics, defect)

Description

[Cornel Ionce [:noni] [Hubs QA]]

Reproduced with Firefox 44.0b8 (build ID 20160111185352) on Ubuntu 12.04 32-bit

STR
*prequisite: user has a Firefox account
1. Launch Firefox with clean profile.
2. Log in using a Firefox account.
3. Go to about:preferences#sync and click "manage Account"
4. Click "Add" an account picture.
5. Click anywhere outside the pop-up.
6. Hover over the pop`up.

Expected Results
The UI is properly displayed, no glitches can be seen.

Actual results
The add picture screen is filled with glitches.
Screenshot: http://i.imgur.com/5oxrbUM.jpg


Additional notes:
Reproducing with latest Nightly (20160111030207), latest DevEdition (20160112004003) and Firefox 43.0.4 (20160105164030).
This is a regression, it does not reproduce on Firefox 36.
Will track down a regression range as soon as time permits.

Comment 1

[Chris Karlof [:ckarlof]]

I can't seem to reproduce on Mac OS X in current Nightly. Maybe this is a Linux only issue?

Comment 2

[Cornel Ionce [:noni] [Hubs QA]]

This is indeed a Linux specific issue.
I've managed to track down a regression range for it:

Last good buildID: 20150416030209
First bad buildID: 20150417030200

Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a35163f83d22&tochange=51e3cb11a258

Comment 3

[Shane Tomlinson [:stomlinson]]

I am unable to reproduce w/ Firefox 44 (current release) on Ubuntu 15.04 64. Do you still see this Cornel?

Comment 4

[Cornel Ionce [:noni] [Hubs QA]]

Mozilla/5.0 (X11; Linux i686; rv:44.0) Gecko/20100101 Firefox/44.0

Yup, I'm still seeing this on Firefox 44 (build ID 20160123151951) on Ubuntu 12.04 x86 although not everytime (3 out of 5 tries it's there).

Comment 5

[Vlad Filippov (:vladikoff)]

I checked 3 different versions of Ubuntu 32-bit and 64-bit and still not able to reproduce.

Could you please try in latest stable (44) and let us know if this still happens? 

Maybe I'm missing some steps to clearly see the bug.

Comment 6

[Cornel Ionce [:noni] [Hubs QA]]

Attachment: Video with the issue occurring

I still reproduce this on Fx 44.0.2, build ID: 20160210153822.
I've reproduced it on two different machines, both running Ubuntu 12.04 x86.
Attached a video with the issue occurring.

Comment 7

[Jim Mathies [:jimm]]

this looks gfx related. Milan, can you ask someone to investigate?

Comment 8

[Vlad Filippov (:vladikoff)]

Clearing need info from me because this seems gfx related. Maybe providing the GPU configuration might help?

Comment 9

[Milan Sreckovic [:milan] (needinfo for best results)]

Does this happen on Linux if you set layers.acceleration.force-enabled in about:config to true (other things may break, but just to check)?  Does it happen on another platform if you set layers.acceleration.disabled to true instead (so, layers.acceleration.force-enabled back to false)?

Comment 10

[Cornel Ionce [:noni] [Hubs QA]]

I was unable to reproduce it on Windows 10x64 and Mac OS X 10.9.5 with layers.acceleration.disabled set to true.

Also, not reproducing on the Ubuntu 12.04 machine with layers.acceleration.force-enabled set to true.

Comment 11

[Milan Sreckovic [:milan] (needinfo for best results)]

With that, chances are the regression range from comment 2 is because that's where we changed the Linux compositor to OMTC (bug 994541), and it's something that goes away when we use OpenGL compositor on Linux, but also when we use software compositor on non-Linux platforms.

Edwin, can you reproduce this?

Comment 12

[Edwin Flores [inactive from 2016-12-01] [:eflores] [:edwin]]

I can't reproduce this.

Cornel, could you post the output of about:support please?

Comment 13

[Cornel Ionce [:noni] [Hubs QA]]

Attachment: about:support

Sure, here is my abbout:support details

Comment 14

[Milan Sreckovic [:milan] (needinfo for best results)]

Moving to graphics while we're sorting this out.

Comment 15

[Edwin Flores [inactive from 2016-12-01] [:eflores] [:edwin]]

Still not able to reproduce.

Everything is pretty standard in the attached about:support. Nothing is hardware accelerated so I think this is unlikely to be hardware-dependent; just really weird timing.

Comment 16

[u279076]

Is this still reproducible for anyone?

Comment 17

[Edwin Flores [inactive from 2016-12-01] [:eflores] [:edwin]]

No response for three months. Resolving incomplete.