1344620 - Menus (right-click, hamburger, top) do not open

Status: RESOLVED WORKSFORME

(Core :: Widget: Gtk, defect)

Description

[Matthew Flaschen]

Attachment: upstream_trace.txt

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131

Steps to reproduce:

I'm on Firefox 51 on Debian Jessie.  This is reproducible both on upstream firefox (from getfirefox.com) and on the Debian-packaged one.

1. Create a fresh profile.
2. Go to example.com (or any other site)
3. Try to open right-click menus, the menus at the top, and the hamburger menu



Actual results:

Often these menus (right-click menus, the menus at the top, and the hamburger menu) will not open.

It then sometimes resumes working.



Expected results:

The menus should open normally each time.

Comment 1

[Matthew Flaschen]

When it's not working, right-clicking on text switches back-and-forth between a caret (I icon) and the mouse pointer.

Comment 2

[Matthew Flaschen]

Also, it even happens on a completely fresh system user (so it's own ~/.mozilla).

Comment 3

[Tooru Fujisawa [:arai]]

any chance it's opened but somehow not visible there?
there were following issues:
  * menu is opened but transparent
  * menu is opened in different monitor

so, can you check the following things?
  1. can you click the menu item (supposing it's transparent but is there) ?
  2. do you have multiple monitor?  if so, do you see the menu in different one than firefox is opened?

Comment 4

[Karl Tomlinson (:karlt)]

Comment on attachment 8843838 [details]
upstream_trace.txt

>(firefox:15118): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

These are disturbing messages.  Did these messages appear and/or the menu problems happen when using Firefox versions < 51?

Running with G_DEBUG=fatal-criticals will cause the program to crash on the first such message, which may generate a stack trace with some clues.

Comment 5

[eclig]

Using iceweasel 45.8.0esr-1~deb8u1 on debian jessie 8.7, Graphics card is Intel.

Some additional data points:  It seems that the window manager does play some role.  Using ratpoison I've never got this problem.  Using dwm it happens quite frequently.  Interestingly quiting dwm after the drop-down menus stop working and starting ratpoison (or twm btw) does not make the menus work again.

Opening a new Iceweasel/Firefox window does not help either, the problem is still there.

I do have two monitors (laptop panel and an external monitor), but the laptop panel is disabled.  I shortly enabled the laptop panel to see if the menus open there => nope.

Comment 6

[Hani Yacoub, Desktop QA]

I couldn't manage to reproduce this issue. Since the bug was logged 5 years ago, most likely isn't reproducible anymore for the reporter also.
Closing this bug as resolved: Worksforme.