1805703 - [X11] Tooltips stay and never disappear when Alt+Tabbing in Linux

Status: RESOLVED WORKSFORME

(Core :: Widget: Gtk, defect)

Description

[Julien Wajsberg [:julienw]]

+++ This bug was initially created as a clone of Bug #1798131 +++

I'm using Gnome 3.38 on Debian Stable, and Firefox Nightly 20221213165020.

When I hover the mouse on something with a tooltip (such as a tab in the tab strip, or the hamburger menu), and then switch to another virtual desktop, the tooltip stays displayed and never disappear until I come back to the initial virtual desktop.

This happens with xwayland and without MOZ_GTK_TITLEBAR_DECORATION=system.

Comment 1

[Julien Wajsberg [:julienw]]

Here is a profile with logs: https://share.firefox.dev/3YmuaQi

Indeed I don't see the leave notify log...

Comment 2

[Julien Wajsberg [:julienw]]

Attachment: aboutsupport.json

Comment 3

[Julien Wajsberg [:julienw]]

(In reply to Julien Wajsberg [:julienw] from comment #1)

Here is a profile with logs: https://share.firefox.dev/3YmuaQi

Indeed I don't see the leave notify log...

In this profile I did 2 things while the tooltip was displayed:

• first I switched my virtual desktop
• then after coming back to the initial desktop, I changed my foreground window with alt-tab.

In both cases the tooltip stayed displayed but I expected that it would go away.

Comment 4

[Emilio Cobos Álvarez (:emilio)]

Does it happen with pure x11?

Comment 5

[Julien Wajsberg [:julienw]]

Just tried, and yes it happens with pure x11 as well.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1756903

Comment 7

[Emilio Cobos Álvarez (:emilio)]

Can you confirm this only happens if you have MOZ_USE_XINPUT2=1 in the environment? I could repro with that.

Comment 8

[Julien Wajsberg [:julienw]]

Yeah I believe you're right.
I definitely have this in my environment.
And when I run with MOZ_USE_XINPUT2=0 then the bug doesn't appear anymore.

Somewhat confusingly I initially ran with MOZ_USE_XINPUT2= (with no value), which (I think) should have also reset the option, but according to the code this does also set the value just like using 1.

(in these tries I always had MOZ_ENABLE_WAYLAND= too, to make sure that I was using xwayland).

Comment 9

[Mathew Hodson]

This looks like a duplicate of bug 1809029 and would then be fixed by bug 148624

Comment 10

[Emilio Cobos Álvarez (:emilio)]

Julien can you confirm?

Comment 11

[Julien Wajsberg [:julienw]]

I'm not running on wayland atm (maybe since I enabled some nvidia drivers) but I don't have the issue here.
I'll have to double check on my other computer. Leaving the NI for now.

Comment 12

[Julien Wajsberg [:julienw]]

On my second computer I use wayland and I don't see the issue on stable v118. But the fix is in v119 so I guess this isn't proof :-)
Let me try to trigger xwayland.

Comment 13

[Julien Wajsberg [:julienw]]

With xwayland, still on v118, I still don't see the issue. So I'm not sure how to confirm properly that it's been fixed in v119.
The good news is that I don't reproduce at all, be it on X11 (on my first computer) , wayland or xwayland.

All my tests have been with MOZ_USE_XINPUT2=1.

I also looked with ESR v115 and I have the same result. So I'm not sure what fixed this in my case.
But I believe we can close the bug.