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

Steps to reproduce:

See the attached picture for the issue.

This often happens when moving a Firefox window from one monitor (vertical) to my other monitor (horizontal). Firefox never recovers from this issue (and often also becomes unresponsive) and I have to kill and restart. This started with the most recent release (11 days ago), and I've just been to lazy to file (pkill firefox and restart has been a pain, but "good enough to get by").

==============================snap info===================================
arc~ snap info firefox
name: firefox
summary: Mozilla Firefox web browser
publisher: Mozilla✓
store-url: https://snapcraft.io/firefox
contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla
license: unset
description: |
Firefox is a powerful, extensible web browser with support for modern web application
technologies.
commands:

• firefox
• firefox.geckodriver
  snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  tracking: latest/stable/ubuntu-21.10
  refresh-date: 11 days ago, at 17:16 MDT
  channels:
  latest/stable: 102.0.1-1 2022-07-08 (1551) 169MB -
  latest/candidate: 102.0.1-1 2022-07-07 (1551) 169MB -
  latest/beta: 103.0b9-1 2022-07-15 (1578) 171MB -
  latest/edge: 104.0a1 2022-07-15 (1581) 181MB -
  esr/stable: 91.11.0esr-2 2022-06-28 (1501) 161MB -
  esr/candidate: 102.0.1esr-1 2022-07-11 (1568) 169MB -
  esr/beta: ↑
  esr/edge: ↑
  installed: 102.0-2 (1498) 169MB -

==================================lscpu==============================
arc~ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 43 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 12
On-line CPU(s) list: 0-11
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 5 2600 Six-Core Processor

===============Ubuntu-provided default gnome extensions================
arc~/workspace/cloud-init(holmanb/ignore|…) gnome-extensions list --system
[email protected]
[email protected]
[email protected]
arc~/workspace/cloud-init(holmanb/ignore|…) gnome-extensions list --enabled
[email protected]
[email protected]
[email protected]

Actual results:

See the attached picture for the issue.

This often happens when moving a Firefox window from one monitor (vertical) to my other monitor (horizontal). Firefox never recovers from this issue and I have to kill and restart.

Expected results:

I shouldn't have to kill and restart firefox hourly to use it.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

This bug appears to be heavily correlated to maximizing the window.

Is this on X11 or Wayland? Can you attach the contents of about:support?

It'd be great if you could test whether a build from https://nightly.mozilla.org repros the issue. I made a variety of fixes in that area (bug 1780372, in particular, but also bug 1773118 etc), so maybe it's fixed there already.

Thank you!

Thanks, so you're using XWayland. Does using native Wayland (launch firefox with MOZ_ENABLE_WAYLAND=1 firefox make it any better?).

From IRC, it seems that keeping the Snap package but running as Wayland would avoid the bug? Reporter is keeping an eye and will update the issue.

(In reply to Emilio Cobos Álvarez (:emilio) from comment #5)

Thanks, so you're using XWayland. Does using native Wayland (launch firefox with MOZ_ENABLE_WAYLAND=1 firefox make it any better?).

From IRC discussion, issue went from "easy easy" to repro with XWayland to "so far can't reproduce anymore" with Wayland. Reporter said he's going to keep an eye on that and will update the bug.

Thanks Alexandre LISSY (:gerard-majax) and Emilio Cobos Álvarez (:emilio)!

Since launching with MOZ_ENABLE_WAYLAND=1 snap run firefox a couple of hours ago, I haven't had any issues yet (with constant usage). Given how easy it was to repro previously, I'm pretty confident this resolves the issue for me.

I can update this bug if I get a repro, but at this point I expect that is pretty unlikely.

The severity field is not set for this bug.
:gerard-majax, could you have a look please?

For more information, please visit auto_nag documentation.

Brett, it has been two months, can you confirm Wayland fixed it?

can you confirm Wayland fixed it?

I am using the 106.0b8 version (snap installed) and have had no problems since switching to it.
I'm happy to test another version if desired.

Firefox is now defaulting to Wayland on release since 121. As this bug is a limitation of XWayland, we cannot fix it.