Among the Firefox Wayland bugs, one of the top crash bugs is over a lost connection to a Wayland compositor. For dealing with it is to have a proxy between Firefox and the Wayland compositor to cache messages and prevent compositor message queue overflows.

  • MentalEdge
    3•11 months ago

    I had to force it to run in xwayland because in wayland it no longer remembers window positions, so with wayland it was opening all my windows in a big pile on the current desktop, instead of putting them in the positions and on the desktops they belong.

    • aard
      8•11 months ago

      That sounds more like a compositor problem - typically a client should not have control over where windows are placed, and that X11 allowed that got heavily abused with negative impact on UI. Wayland fortunately fixed that, so it is now up to the compositor where to place windows. Those can send hints, but the compositor is free to ignore them.

      In your situation your compositor should remember where to stick the windows.

      • MentalEdge
        4•11 months ago

        Kwin. It works with xwayland, doesn’t with wayland, I’d love a solution, but I found nothing.

          • MentalEdge
            1•11 months ago

            Doesn’t the window title change on firefox depending on tab or even web-page?

            • @[email protected]English
              1•11 months ago

              Yeah, if you want certain pages in certain screens it would work, and then they’d stay there

              • MentalEdge
                1•11 months ago

                And if I ever browse away from that page and forget to return to it before closing firefox…

                This has a million caveats and isn’t even close to a solution for how I use firefox. Each desktop has their own windows and I want them to stay there because the tabs open are relevant to that desktop.

                Meanwhile forcing xwayland, just works.