Dan Jacobson Reporter
	Description • 11 years ago

User Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20130726 Firefox/24.0 Iceweasel/24.0a2 (Nightly/Aurora)
Build ID: 20130726004002

Steps to reproduce:

After a while, in all tabs./windows
1. The right mouse click no longer does anything.
2. The left mouse click on File Edit View ... toolbar just flashes that toolbar item's name, but does not open up that item's submenu.

Typing ALT F, ALT E, ALT V, etc. also just flashes that item.



Expected results:

One needs to restart firefox to get things working again.

	Dan Jacobson Reporter
	Comment 2 • 11 years ago

Basic left link clicking is unaffected.

	[:Aleksej]
	Comment 3 • 11 years ago

Does it happen with builds from Mozilla?
Window manager?

	Manuela Muntean [Away]
	Comment 4 • 11 years ago

Could you please try the following, to see if you still reproduce the issue :

1) try this with a clean profile: http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

2) running in Safe mode: http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

	Dan Jacobson Reporter
	Comment 5 • 11 years ago

All I know is it happens on several of my machines,
usually after an hour or so of using Facebook.

I use clean installations of Firefox. Virgin profiles.

The only addon is adblock plus.

	Dan Jacobson Reporter
	Comment 6 • 11 years ago

The workaround here on linux (noting that File > Quit is no longer clickable, as one cannot open the File menu anymore due to the bug) is
$ killall firefox
$ firefox

	Dan Jacobson Reporter
	Comment 7 • 11 years ago

That restores our session pretty much intact.
One should perhaps submit any half filled forms before doing that though, as at least left clicking Submit buttons still works.

	Dan Jacobson Reporter
	Comment 8 • 11 years ago

Happened in -safe-mode too today after about an hour using Facebook.

	Dan Jacobson Reporter
	Comment 9 • 11 years ago

Wait, it appears I don't need to restart Firefox. All I need to do is close each and every Facebook tab (and then open them back up again if I want) and the problem is gone.

	Dan Jacobson Reporter
	Comment 10 • 11 years ago

Today it happened when NOT browsing Facebook.
So all I still know is it takes about an hour of browsing to cause the bug.

	Dan Jacobson Reporter
	Comment 11 • 11 years ago

Today closing each and every Facebook tab didn't help. One must close all tabs (and thus quit, and later restart Firefox.)

	LaurentS
	Comment 12 • 10 years ago

I get the same issue. After some time (cannot be more accurate than this, but an hour is probably a minimum) menus won't open if clicked on. The "+" sign to open new tabs has no effect (CTRL+t still works).

What is interesting is that I get the same issue in Thunderbird, with exact same symptoms (though the problem does not occur in both apps at the same time!), but no other application. So I'm guessing some shared lib. Running Linux Mint Petra with Mate as window manager. Firefox 29 and Thunderbird 24.5.0, but the issue has been around for a while.

I need to restart the program to fix the issue.

	LaurentS
	Comment 13 • 10 years ago

Issue filed for Thunderbird here: https://bugzilla.mozilla.org/show_bug.cgi?id=1032619.

	beanladen
	Comment 14 • 10 years ago

This is very prominent in all versions since 4.x, just don't touch the 
computer for an hour, then both thunderbird and firefox will not open any
of its menus, last tested was 31.2.0 (TB and FF) on Solaris x86 version,
profile/safe makes no difference. The bug is very reliably reproduceable 
since 30.x, before it was a little bit random to get there.

	beanladen
	Comment 15 • 10 years ago

See also old bug #637023 and bug #642232, it first appeared in the bookmark 
menu.

	beanladen
	Comment 16 • 7 years ago

This still happens in Firefox ESR 45.7 (Opensolaris version). Just prominently happened when logging on the github login page to this site, menus 
locked, and even back history completely stopped working (firefox was just a few minutes up, no page visited before). As reported before, this
happens after a significant time of inactivity automatically, or seems to be triggered instantly after logging into specific newer sites, as this
github page, or, e.g., https://mein.stadtmobil.de/. Very pesky, annoying problem. I think 1344620 and 1058058 are just plain duplicates of this bug.

	beanladen
	Comment 17 • 7 years ago

Just adding that this does not only affect the firefox menus, but all forms menus on loaded webpages too.

	Wayne Mery (:wsmwk)
	Comment 18 • 7 years ago

A large number of mouse bug reports end up closing as invalid. https://mzl.la/2uUGRYd

Dan, does this still reproduce for you?

	beanladen
	Comment 19 • 7 years ago

Still very regularly occuring and reproducible on FF 52.0.2 (Solaris x86). Far from being invalid...

	Dan Jacobson Reporter
	Comment 20 • 7 years ago

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #18)
Frankly these days I don't usually manage to use Firefox for a whole hour unless I'm on some Big Iron CPU, so can't tell you.
However as you see in Comment 19, others say yes. So I'll unsubscribe...

	Dmitry Alexandrov
	Comment 21 • 6 years ago

Have to report that I also encounter this problem on daily basis on Debian GNU/Linux Stretch running X11, and using either Debian’s build of Iceweasel / Firefox (now 52.9.0), Mozilla’s build of released Nightly (now 58.0.2), or Mozilla’s build of beta Nightly (now 62.0b16).

To recite:

After a while of running an instance of Firefox any sort of popup window (main menu, context menu, address bar completion popup, etc) stops being usable: they flash for a moment and immediately close.  This makes unusable a good half of browser features.

I was not able to figure out any specific pattern that leads to the bug.

In particular, I do not see connection with any website (in particular with aforementioned Facebook, which I do not visit).

In the linked thread there was a suggestion that it might be provoked by suspending a system.  As for me, suspending a system does not lead straightforwardly to a problem.

Restarting browser (in a sense of “>> restart” command) does _not_ always help.  But sometimes do.

Quitting browser and starting it anew does always help for a while.

Unfortunately, I did not find any guide on how to enable debug output for Firefox’s UI.  Standard error output with NSPR_LOG_MODULES='all:3' shows literally nothing.  With 'all:5' there are only messages about loading various libraries (presumably successfully).

	Dmitry Alexandrov
	Comment 22 • 6 years ago

(In reply to [:Aleksej] from comment #3)
> Window manager?

In order to reduce possibility of blaming other software, I just reproduced it with *no* window manager at all.

Moreover, I seemingly found a quick way to reproduce the bug for current Mozilla’s builds on my system: that is exactly to run it with no WM!

This does not apply to Debian’s build of Firefox 52.9.0, which does not immediately run into problem when started with no WM.