Closed Bug 1973354 Opened 9 months ago Closed 9 months ago

Intermittent unresponsiveness of tab close buttons, address bar, and toolbar UI in Firefox on Wayland — fixed by dragging a tab

Categories

(Core :: Widget: Gtk, defect)

Firefox 139
defect

Tracking

()

RESOLVED DUPLICATE of bug 1955112

People

(Reporter: liormor001, Unassigned)

Details

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

Steps to reproduce:

Steps to Reproduce:

Run Firefox under Wayland (MOZ_ENABLE_WAYLAND=1)

Browse normally for 5–30 minutes (no specific trigger)

Eventually, certain UI elements become unresponsive:

    Clicking the ❌ on tabs does nothing

    Navigation bar buttons and address bar stop responding

Dragging a tab (even slightly) restores full interactivity immediately

Actual results:

Observed Behavior:

Only top-level widgets freeze (tab close buttons, address bar, nav buttons)

Mouse events no longer reach those widgets until a redraw is forced

Terminal logs (with GDK_DEBUG=events) show no pointer events delivered when UI is frozen

Observed error in console during freeze:

[GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt

Workaround:

Dragging a tab triggers a redraw that restores UI responsiveness

Expected results:

All UI elements remain responsive during normal operation

Additional Notes:

Disabling hardware acceleration has no effect

Happens with clean Firefox profile

Both Snap and Deb builds affected

Still occurs with GTK 4 backend enabled

Still occurs with MOZ_WEBRENDER=1, MOZ_ACCELERATED=1

Issue is intermittent, not reliably reproducible on demand

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.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Dupe of Bug 1955112.

Status: UNCONFIRMED → RESOLVED
Closed: 9 months ago
Duplicate of bug: 1955112
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.