Closed Bug 1965488 Opened 11 months ago Closed 11 months ago

Buttons / Navbar becomes unresponsive

Categories

(Core :: Widget: Gtk, defect)

Firefox 138
defect

Tracking

()

RESOLVED DUPLICATE of bug 1955112

People

(Reporter: tonytmurray, Unassigned)

Details

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

Steps to reproduce:

After several minutes (perhaps 10/ 20) regular browsing, typical (for me) websites. (I am a website developer)

I use Linux, Kubuntu 04/2025 edition, Wayland

Restarting the browser solves the issue below

Actual results:

The navbar buttons (back button, refresh button, and whatever buttons I have added) along with the navigation entry bar, and search bar all become 'inactive' / unresponsive.
-- (oddly) .. except for the 'Home button'
-- The tab bars are normal, the main browser window is normal

Sometimes the browser freezes

I tried disabling all extensions, doing a full browser refresh.
Also disabled hardware acceleration.
Also tried browser chrome debugging (Ctrl-Alt-Shift-I)
I see error message
TypeError: body is null receiveMessage resource://gre/actors/ThumbnailsChild.sys.mjs:29 at some point -- it is not clear if this error message is related to the subsequent navbar freeze.

Expected results:

Buttons should operate normally. It is a 'Blocking bug' - interferes with my work as a website developer. (And also interferes with regular browsing)

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

I think this is a version of bug 1955112. Dragging a tab and dropping it seems to restore the working state. If it doesn't please re-open this.

Status: UNCONFIRMED → RESOLVED
Closed: 11 months ago
Duplicate of bug: 1955112
Resolution: --- → DUPLICATE

Yes seems to be the same as bug 1955112, and dragging a tab works - is a useful workaround - thanks for the tip!

You need to log in before you can comment on or make changes to this bug.