1717316 - [layout.css.devPixelsPerPx] Regression in display of popups and context menus (flickerling, moving around, don't show up, crash firefox)

Status: RESOLVED DUPLICATE of bug 1708709

(Core :: Widget: Gtk, defect, P3)

Description

[Simonas Kazlauskas [:nagisa/:simukis]]

Attachment: Context menus in weird places, flickering and crashing

Recently (within past couple of days) the context menus and extension popups have started failing to draw correctly under sway. In some cases, when interacting with plugin popups, firefox crashes:

https://crash-stats.mozilla.org/report/index/3f8a1582-21fe-4d49-9c6f-ca5160210619

See the attached video with the demonstration.

Comment 1

[Simonas Kazlauskas [:nagisa/:simukis]]

Neglected to mention: this is on sway.

Comment 2

[Jan Alexander Steffens [:heftig]]

Can you do a bisection using mozregression?

Comment 3

[Simonas Kazlauskas [:nagisa/:simukis]]

I made an attempt to run mozregression-gui, without great success. Once I managed to get it to the point of not complaining about missing system libraries, it simply crashed:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f63e103d5ba in raise ()
   from /nix/store/1jn6apz0fa9h9x7rl3v6vwiymwnjznwv-glibc-2.32-40/lib/libpthread.so.0
(gdb) bt
#0  0x00007f63e103d5ba in raise ()
   from /nix/store/1jn6apz0fa9h9x7rl3v6vwiymwnjznwv-glibc-2.32-40/lib/libpthread.so.0
#1  0x000056357c4ff213 in ?? ()
#2  0x000056357c4fd15d in ?? ()
#3  0x00007f63e0e90ded in __libc_start_main ()
   from /nix/store/1jn6apz0fa9h9x7rl3v6vwiymwnjznwv-glibc-2.32-40/lib/libc.so.6
#4  0x000056357c4fb50a in ?? ()

I'll see if I can get the CLI tool running...

Comment 4

[Simonas Kazlauskas [:nagisa/:simukis]]

I think I spent sufficient number of hours trying to run/package mozregression. Got to the point of gleam-sdk at which point there was this pesky setup.py trying to download stuff off internet past the build sandbox through cargo. I'll leave it at that and you'll have to trust my word that the regression has occurred somewhere in between

Nightly 90.0a1 (linux-x86_64 tarball checksummed 5ec61547d7498c2efc807170f7db512cb9c8528f84e8c7edd3bf2c9c9c3eac94)

and

Nightly 91.0a1 (linux-x86_64 tarball checksummed 2643886d6393b132df144e9633edaea6b1a67663fb95ba28d1c488f7d288081e).

That's all I know.

Comment 5

[Martin Stránský [:stransky] (ni? me)]

Please re-test when Bug 1717451 lands, I can investigate it then.

Comment 6

[Simonas Kazlauskas [:nagisa/:simukis]]

Still an issue with nightly I got just now (tar.bz2 checksummed 15805c0382b5287f9fbb5ee0b7ab71f00b250a32f2738b26575bc9d484c30b58). No idea how to check if it contains Bug 1717451 though. Will test tomorrow or day after tomorrow.

Comment 7

[Martin Stránský [:stransky] (ni? me)]

Can you please test mutter compositor on the same environment? How-to is here:
https://wiki.gnome.org/Initiatives/Wayland/GnomeShell/Testing
(run as nested subcompositor).
Thanks.

Comment 8

[Simonas Kazlauskas [:nagisa/:simukis]]

Attempts to run a nested gnome-shell and/or mutter fail with

(mutter:262524): Clutter-CRITICAL **: 00:20:24.519: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.

(mutter:262524): mutter-WARNING **: 00:20:24.519: Failed to create backend: Unable to initialize Clutter

This seems relevant, but I'm otherwise unable to test this, because of this issue. I also attempted to run gnome-shell from a tty, but it refuses to start without any output.

Comment 9

[Martin Stránský [:stransky] (ni? me)]

Does plain mutter session works for you? Run as:

mutter --nested

and you should be able to run Firefox on it with WAYLAND_DISPLAY=wayland-1

I just tested that on Fedora 34 and it works for me but I have Gnome installed.

Comment 10

[Simonas Kazlauskas [:nagisa/:simukis]]

This appears to work okay under gnome-shell/mutter over here as well.

Comment 11

[Martin Stránský [:stransky] (ni? me)]

Thanks, moving to Sway tracker then. Do you mind to report it at Sway bug tracker?

Comment 12

[xpduyson]

Attachment: Firefox 91 flickering menu on Gnome 40 Wayland

I've just upgraded to Firefox 91 and I can reproduce this issues on Gnome 40 Wayland as well. Change layout.css.devPixelsPerPx to any value over 1.0 will make all context menus behave weirdly. A workaround is to use Firefox in XWayland.

Comment 13

[xpduyson]

I want to add more information to my comment above.

• My Firefox instance was running with MOZ_ENABLE_WAYLAND=1
• This bug doesn't happen if the user increase dpi with fractional scaling (the "zoom" percent in display settings).
• It only happen if user change the system font dpi. If I understand correctly, the default value -1.0 of layout.css.devPixelsPerPx only response to "text-based scaling", for example, increasing font dpi on KDE or changing font scaling factor on Gnome. So any changes to layout.css.devPixelsPerPx will trigger this bug.

Comment 14

[m.j.lbach]

I also have this bug (in sway), but an additional piece of information is that it only appears for non-integer values of layout.css.devPixelsPerPx. 1.0 and 2.0 are fine, but 1.5 is not.