1558068 - can't click on "Open Menu", "More Tools" and other icons on second X11 display

Status: UNCONFIRMED

(Core :: Widget: Gtk, defect, P3)

Description

[Henrique Martins]

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0

Steps to reproduce:

On a certain system I have two independent X11 displays, :0.0 and :0.1.
If I start as "DISPLAY=:0.0 firefox -P profile --safe-mode", clicking on the OpenMenu, MoreTools, or icons I placed to the left of MoreTools, works fine.
If I start as "DISPLAY=:0.1 firefox -P profile --safe-mode", clicking on any of those doesn't do anything. Can't use any of that functionality.

Actual results:

See steps above, mouse clicks don't work on certain buttons/icons. Also fails in most of the icons in the location bar. Home, reload, back, forward seem to work.

Expected results:

Working buttons/icons

Comment 1

[David Sacal]

Hi Enrique,

Unfortunately i'm not able to reproduce the inconvenient on my end. Please download Firefox Nightly from here: https://nightly.mozilla.org/ and retest the problem.

If you still have the issue please create a new profile, you have the steps here:https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Please test if the issue is reproducible in safe mode, here is a link that can help you:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Finally, if the behavior is always the same reach us out back with detailed steps

Regards
David

Comment 2

[Henrique Martins]

That's Henrique, i.e. Enrique with an extra (silent) H in the beginning.
Note that in my description I stated that I started firefox in safe-mode in both cases.
There could be something wrong with the profile I used, but the same profile was used pointing at the two displays (well, I didn't save and restore that profile between invocations, thus they could be slightly different, if firefox messed with it). As it was the same profile I was expecting it to either fail or work in both instances.
Interestingly enough, after a while, not sure under what circumstances, it starts working, but upon restart it is normally broken.
This started a couple of months back, it used to work fine. Also, at work, where I have four independent display (:0.0 through :0.3) I've never noticed this problem.
When I noticed the problem for the first time, I copied the profile I use with display :0.0 over the one I use for :0.1, edit it to point to the proper base path, and the problem went away for a while, only to come back later.
I'll chime in with more details when I can debug this further, probably on a weekend. Thanks.

Comment 3

[David Sacal]

Hi again Henrique, because we don't have that environment with the 2 independent X11 displays, I'm not sure how we can reproduce this issue on our end but maybe one of our devs know more about it.
I will set the component for it to Core Widget gtk but it seems it might belong in the Unsupported systems, not sure though.

Regards
David

Comment 4

[Henrique Martins]

Maybe this should be closed on put on a frozen state, until I have time to try to compile Firefox and debug this myself.
Couple more observations:

• it eventually starts working, no idea under what circumstances, sometimes it works right off the bat
• it never happens on my work system, where I have 4 independent screens, similar setup, probably different card drivers
  Strange

Comment 5

[BugBot [:suhaib / :marco]]

The priority flag is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 6

[Henrique Martins]

Just found a way to make it work that may or not point to the cause of the problem.
If I unmap (iconize) the window, and remap it again (un-iconize) it starts working.