1. 25
  1.  

  2. 10

    Screen sharing has proven to be a bit more difficult than expected on Wayland-based setup.

    In addition to the setup described in this blogpost, I had to make the following modification:

    1. Thanks to systemctl --user status xdg-desktop-portal-wlr.service, I discovered slurp was a necessary dependency.
    2. I had to add export MOZ_ENABLE_WAYLAND=1 and export XDG_CURRENT_DESKTOP=sway to my .zshrc file
    3. The /etc/pipewire/media-session.d/media-session.conf file was outdated. Using pacdiff, I was able to replace it by its pacnew counterpart. The key difference between the two files is the metadata module. The following lines has to be uncommented.
    { name = libpipewire-module-metadata }
    

    And after all that, it finally worked on Firefox.

    1. 4

      I run a mostly-full wayland setup on Arch Linux, and was recently bit by this bug that causes Audacity to OOM the system only when it runs under Wayland. The workaround is to run it in under Xwayland. Sigh.

      https://bugs.archlinux.org/task/67547?project=5&string=audacity

      Detecting XWayland with xlsclients

      xeyes is my favorite way to detect whether a client is running under Xwayland. It’s not super practical in every situation, but it sure is more fun.

      1. 4

        https://codeberg.org/dnkl/foot is a good wayland terminal. It’s packaged in debian and it doesn’t mind old graphic cards.

        1. 2

          I have a similar sway-based setup I do login into to try every few months.

          Unfortunately, I typically last very little in there due to minor but unbearable annoyances.

          E.g. when using chromium (not forced to wayland, so I presume it still defaults to X even today, which is in itself sad) and moving mouse above the tab bar (into i3’s window title, which is also a tab bar), the browser thinks mouse is still in the window, stuck at the topmost position. This causes tooltip for a browser tab to pop up. This happens a lot and is a major nag.