Menus don't get displayed (Linux, Wayland)
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr153 | --- | unaffected |
| firefox159 | --- | unaffected |
| firefox160 | --- | unaffected |
| firefox161 | --- | affected |
People
(Reporter: Leico, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:161.0) Gecko/20100101 Firefox/161.0
Steps to reproduce
This bug appeared after updating Nightly on 2026-11-03. I'm running openSUSE Tumbleweed with KDE on Wayland. The issue does not happen on X11. It also happens in troubleshooting mode (which required a blind click because the dialog window to open Firefox in safe-mode was not rendered).
Using mozregression resulted in the following report:
4:09.45 INFO: Last good revision: f3d906516ae4bc4a22600de3c0525d8f9901eb51
4:09.45 INFO: First bad revision: fb94d335c65594e2ada72997a5cf01c729fc7315
4:09.45 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f3d906516ae4bc4a22600de3c0525d8f9901eb51&tochange=fb94d335c65594e2ada72997a5cf01c729fc7315
Actual results
When trying to open a menu (hamburger menu, overflow menu, or any context menu) the menu does not appear at all. Sometimes it appears in a glitched form.
Expected results
Menus should be displayed.
Comment 1•14 days ago
|
||
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.
Comment 2•14 days ago
|
||
Please attach your about:support.
Is that a recent regression? Can you use https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Use_Mozregression_tool to find the broken commit?
Thanks.
Comment 3•14 days ago
|
||
Ah cool, I see you already did the mozregression check!
Updated•14 days ago
|
Comment 5•14 days ago
|
||
Which KDE version do you run? I don't see that on Fedora 44.
Thanks.
Comment 6•14 days ago
|
||
Netflate, is it possible that there's a regression on old KDE systems?
I've added the about:support to the attachments. Here is the info from KDE's info center
Operating System: openSUSE Tumbleweed 20261102
KDE Plasma Version: 6.8.2
KDE Frameworks Version: 6.31.0
Qt Version: 6.12.0
Kernel Version: 7.3.1-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD JUNIPER
Manufacturer: Gigabyte Technology Co., Ltd.
Updated•14 days ago
|
Updated•13 days ago
|
Unfortunately this is a KDE problem: kwin relies on the driver to reject strides it can't handle, and old AMD (r600) silently renders garbage instead, while newer AMD drivers reject them properly.
fix on the Firefox side would be to align the stride to 256 bytes, like Qt does. The stride is hardcoded as width * bpp in several places. Here's what I found, there might be more, but I think that's all:
- SHMBufSurface.cpp: CreateImpl, UploadTexture, Lock, CreateWlBuffer, GetAsSourceSurface
- WindowSurfaceWaylandMultiBuffer.cpp and NativeLayerWayland.cpp, where the front buffer is copied
I guess gfx::GetAlignedStride<256>() can compute it, and BufferSurface has mStrides[] to store it.
Really sorry about that. I'm not affiliated with KDE. I took their approach as the reference and almost made the same mistake.
Comment 10•13 days ago
|
||
(It affects Plasma >= 6.7 with old amd gpus, as far as I can tell pre-2012 ones (r600 driver) )
Comment 11•13 days ago
|
||
We don't use stride at all - we just align the memory to page size and allocate the whole image at beginning. The stride is zero.
Comment 12•13 days ago
|
||
I don't know how to fix that as we don't use stride/align at all for the SW rendering.
Let's revert it for now.
Comment 13•13 days ago
|
||
Regressor, Bug 2087615 was backed out. https://hg.mozilla.org/integration/autoland/rev/0c094062a7edb73d80f46516d91778a3856d9413
Comment 14•13 days ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Updated•12 days ago
|
Description
•