this post was submitted on 06 Dec 2025
23 points (96.0% liked)
Linux
10673 readers
442 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That would make it a different problem than what I saw. Either your compositor has bugs not present in its xwayland, or firefox has bugs in its wayland implementation that don't occur under x11. Seeing this is snap, that could also be causing the issue.
xwayland will be supported for a long time to come, so this would only affect users that don't know about this "fix" yet. You should be able to use firefox in x11 mode until this is fixed.
It would be good if you could check if this happens with a native (non-snap) firefox installation running on wayland. Ideally also if you could try it in a different dwm, probably kde since you are presumably using ubuntu with gnome.