You are not logged in.
Hi !
I couldn't find anyone reporting this, so I am making this thread partly to know if it is my setup that is somehow f-up, or if there is really an issue worthy of a bug report.
I am on wayland + hyprland (daring I know), and I recently upgraded Firefox from 141 to 142. Since then, The whole UI has been really buggy.
For the most part, it takes the form of : Opening a menu (for example, the burger menu or the menu when right-clicking on a tab), then clicking on an option (like close tab, or "About") instantly close the menu *without* doing what the option was supposed to do.
Worse, sometime, even shortcut seems to fail. For example, I manage to reproduce it fairly reliably ( but not always ) when pinning a google meet tab. The pinned tab become impossible to close : The right click menu does not work, and CTRL+w does not close the tab but switch to the next non-closed tab.
Painting/re-painting seems to be an issue also: Right clicking on a page sometimes leaves the image of the submenu on the page, until the mouse cursor is passed over it.
Downgrading to 141 fixed all of those issues.
I will try to make a video showing the bugs in action, but I need some time to set this up without doxxing myself. Is it a known bug that I somewhat missed ? Does anyone else encountered the same issues ?
Offline
Start Firefox from terminal. Do you see any interesting output? In journalctl, coredumpctl?
Try new Firefox version - 143, new Firefox profile, under new user, in sway or other Wayland compositor, in X server.
What about that video you promised?
Offline
Now that you mention it, my desktop PC has almost the same setup but do not show any sign of those issues. They seem to only occur on my laptop. I will try to circumscribe the issue more today if I have the time.
Offline
Sorry, I didn't have much time to try to debug my setup. For now, I manage to reproduce the issue with the 143 version of FF.
I launched firefox from the terminal and got this line of log when the bug triggers :
[GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt
A quick google search find many report of this error, including in this forum, This one who is solved, this one who is not solved, also this one from endeavour. One thing in common between all these reports : They all seem to be using AMD GPU, which is also the same for me (I have a Framework Laptop 13 AMD Ryzen 7040 Series). I tried some stuff from the various post, but so far no dice.
But at this point, I do suspect and issue more with AMD drivers and less with FF. I already had random crashes where the kernel logs indicated a issue with the AMD driver, so it might be linked.
Edit : I will try a firmware update and see if that helps. If it does not, I am not sure what to do. I guess try to get more detailed logs to report the issue to the amd driver team
Edit 2 : Althouh, there is something strange about the fact that it is working fine with FF 141 but suddendly break with FF 142+. I guess I could try to bisect the issue
Last edited by maeln (2025-09-30 13:01:00)
Offline
Not on hyperland, but on wayland for a long time. Firefox 142+ crashes all the time. It's been over a decade since i've experienced a crash.
Offline