Firefox Nightly will open but when clicked on will not respond
Categories
(Firefox :: General, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox71 | --- | unaffected |
firefox72 | + | fixed |
People
(Reporter: sebastian, Unassigned, NeedInfo)
References
(Regression)
Details
(Keywords: nightly-community, regression)
Attachments
(1 file)
16.48 KB,
application/x-executable
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0 Safari/605.1.15 Epiphany/605.1.15
Steps to reproduce:
It happened after an update no other cause.
Actual results:
When I tried to click on the browser, if I had another window open it would flip to another window. If it was the only window open the browser does not respond to anything.
Expected results:
The browser should have responded and stayed in view.
Reporter | ||
Comment 1•5 years ago
|
||
[Tracking Requested - why for this release]: Because this is the only version affected
Comment 2•5 years ago
|
||
I also have this issue.
72.0a1 (2019-11-22) (64-bit) Linux
The first ferw tabs on any FF window are clickable. The other tabs are not. Nothing in any tab shows a cahnge in cursor when hovering over a link, nor does it register a right-click in the ccontent area, nor can any text be selected. Contetn cannot be scrolled with the mouse wheel. Not even the text menu items work.
Keyboard navigation works, and I can cycle through tabs with ctrl + page up/page down.
Interestingly, the Help -> About window worked normally - I could copy text, the cursor chaged to a hand when hovering a link, etc.
Comment 3•5 years ago
|
||
I wanted to add that it only happened after "restart to update nightly" was selected. Restarting several times has changed nothing.
Comment 4•5 years ago
|
||
Another update: The top left 200px x 200px area of the window (including tabs but excluding window borders) is responsive to mouse inputs. All expected mouse events work - scrolling, right click, link clicking, pointer changing on links, etc.
Comment 5•5 years ago
|
||
Same problem here. I removed some environment variables and it fixed the problem:
- GDMSESSION
- XDG_SESSION_CLASS
- XDG_CURRENT_DESKTOP
- SESSION_MANAGER
- XDG_SESSION_TYPE
- XDG_GREETER_DATA_DIR
- XDG_SEAT_PATH
- XDG_SESSION_ID
- XDG_SESSION_PATH
I'm not sure which one(s) fixed the problem yet. I'll have investigate further.
Comment 6•5 years ago
|
||
Removing XDG_CURRENT_DESKTOP fixes the problem for me. XDG_CURRENT_DESKTOP=XFCE on my system.
Comment 7•5 years ago
|
||
Thanks Gabriel, I can confirm that that fixed it for me as well. My variables was:
echo $XDG_CURRENT_DESKTOP
MATE
echo $XDG_CURRENT_DESKTOP
KDE
Same problem. using "unset XDG_CURRENT_DESKTOP" seems to have fixed it for now.
Updated•5 years ago
|
Comment 9•5 years ago
|
||
Changed the severity because the bug renders nightly completely unusable. There is no way to interact with the browser unless XDG_CURRENT_DESKTOP is unset.
Reporter | ||
Comment 11•5 years ago
|
||
Unfortunately unset XDG_CURRENT_DESKTOP does not work for me. Additionally this bug has only been known to affect a small number of users since this is on Firefox Nightly and only is known to affect Linux users, so therefore it is not known whether the bug also affects users of Mac or Windows on Firefox Nightly.
Comment 12•5 years ago
|
||
I think I got my duplicate comment backwards. 1598873 is a duplicate of this bug. 1598873 should be closed (as duplicate) however, this bug (1598822) is critical. All Firefox Nightly bugs will affect a small number of users because Nightly is a glimpse of the future. If a bug in Nightly were to be ignored, there is a chance it would eventually roll out in the production version of Firefox.
Reporter | ||
Comment 13•5 years ago
|
||
But still this only affects Linux users. It has not been confirmed to affect users of Mac or Windows.
Comment 14•5 years ago
|
||
Confirmed for me (64-bit Debian Testing). Unsetting the XDG_CURRENT_DESKTOP variable solves the problem. I'm on XFCE.
It could be interesting to find which commit caused the problem.
Reporter | ||
Comment 15•5 years ago
|
||
I am on Kubuntu 20.04 and my desktop environment is KDE. It does not work for me.
Comment 16•5 years ago
|
||
I traced the problem with mozregression to this:
Updated•5 years ago
|
Comment 19•5 years ago
|
||
I've marked this as a regression, and thank Eduardo for quickly finding the likely commit.
:mossop's backed out the change.
Comment 22•5 years ago
|
||
Since applying Nightly update 20191123214900, this issue has disappeared for me however, I am not the originator of this bug.
Comment 23•5 years ago
|
||
Confirming that build ID 20191123214900 does not exhibit the buggy behaviour
Updated•5 years ago
|
Comment 25•5 years ago
|
||
Fixed by backout of bug 1596709.
Comment 26•5 years ago
|
||
Has returned in BuildID=20191127114233 (was absent in BuildID=20191126093448)
Comment 27•5 years ago
|
||
Bug 1596709 has been backed out and new Nightly builds requested while Nightly updates have been halted.
Comment 28•5 years ago
|
||
Could you try out this build to see if it works for you?
Updated•5 years ago
|
Description
•