Closed Bug 1961060 Opened 1 year ago Closed 1 year ago

Close tab button randomly stops working [Linux]

Categories

(Core :: Widget: Gtk, defect)

Firefox 138
x86_64
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1955112

People

(Reporter: shtetldik, Unassigned)

References

Details

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

Steps to reproduce:

For some time already with Firefox 138 (beta), close button can randomly stop working. It just does nothing, while you can close the tab with Ctrl-W still. Not sure what triggers it, but once it happens, it remains broken unless you close and restore the Firefox window where it happens. Other windows aren't affected.

OS: Debian testing
KDE Plasma 6.3.4 (Wayland session)
GTK: 3.24.49

OS: Unspecified → Linux
Hardware: Unspecified → x86_64

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

This looks related. When it happens, I see this in dmesg:

amdgpu 0000:48:00.0: amdgpu: VM memory stats for proc RDD Process(622779) task firefox-bi:cs0(620616) is non-zero when fini
amdgpu 0000:48:00.0: amdgpu: VM memory stats for proc firefox-bin(620574) task firefox-bi:cs0(620445) is non-zero when fini

Kernel: 6.14.2
Most recent amdgpu firmware
GPU: AMD Radeon RX 7900 XTX (Sapphire Nitro+)

I'll pay more attention to these errors and will also report it to drm/amd bug tracker.

May be it was coincidental, I got another instance of this without those dmesg messages.

This started happening more frequently now and is pretty annoying.

I do see that with others apps under Gnome too, mainly mplayer.

Martin, are you investigating this as a GTK bug? Other Linux users have reported they're experiencing UI freezes too on Firefox support communities.

Flags: needinfo?(stransky)
Severity: -- → S2
Status: UNCONFIRMED → NEW
Ever confirmed: true

If anyone missed it, one of those links mentions a workaround (besides using Ctrl-W) - rearranging tabs unblocks it.

I think this is bug 1955112, given comment 8.

Status: NEW → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1955112
Resolution: --- → DUPLICATE
Flags: needinfo?(stransky)
You need to log in before you can comment on or make changes to this bug.