Wayland. It comes up a lot: “Bug X fixed in the Plasma Wayland session.” “The Plasma Wayland session has now gained support for feature Y.” And it’s in the news quite …

  • kool_newt@lemm.ee
    link
    fedilink
    English
    arrow-up
    35
    ·
    1 year ago

    I have to use Slack for work and screen sharing doesn’t work when I’m using Wayland.

    • daq@lemmy.sdf.org
      link
      fedilink
      arrow-up
      41
      ·
      1 year ago

      Don’t let Slack launch at startup. As long as it launches after pipewire - everything works. Your can also restart it to fix sharing issue, but that can be a birch if you already started a call.

      • luciferofastora
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        Is there a way to control the launch order? I suppose you could also find a script that waits for a given process to be responsive before launching another, but I’m not sure where I’d insert that either.

        (I’ve been using Ubuntu mostly out-of-the-box so far and just now started having the time and energy to start learning about and fiddling with the internals)

        • vividspecter@lemm.ee
          link
          fedilink
          arrow-up
          13
          ·
          edit-2
          1 year ago

          If it launches via a systemd service, you can perhaps edit the file such that it depends on Pipewire before it launches.

          Or disable the built in startup support and create your own service that does the same.

        • daq@lemmy.sdf.org
          link
          fedilink
          arrow-up
          8
          ·
          1 year ago

          I’m not sure that would work. Pipewire probably starts via system (just takes a while to become functional) and slack is started by KDE. I guess you could just add a delay to slack’s start, but I just start it by hand.

          • luciferofastora
            link
            fedilink
            arrow-up
            5
            ·
            1 year ago

            Starting by hand is fine and I do it with just about anything I need anyway (though I suspect there is still some startup bloat I’ll need to sort out, if I don’t set up an entirely new system somewhere down the line), but don’t underestimate my compulsion to automate what I can (or at least know how to).

            I’m a sucker for automation for automation’s sake :D

      • vancent@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        That has nothing to do with Slack’s screen sharing issues. Screen sharing was broken due to Electron bugs and it’s fixed in Slack 4.34.

        • daq@lemmy.sdf.org
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I’d argue lazy choice of wrapping your website inside chrome instead of building a native app is Slack’s issue.

          I also wonder whether Slack fixed it or just waited for Google to fix it since Slack seems to only have UI designers and no actual devs on their team. They keep pumping out useless UI changes while actual bugs take years to fix.

          • vancent@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            Many Electron maintainers are Slack employees. They’re contributing upstream more than most other companies that use Electron, especially compared to their size.

            • daq@lemmy.sdf.org
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              Could you name a couple? Genuinely interested to check out their contributions.

              Also, I just updated to 4.34.119 and screen sharing is still completely broken. As is typical with Slack.

      • uis@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        As long as it launches after pipewire

        Why? Why plasma nailed own screensharing to audio server? There already are wayland extensions for this.

            • Ullebe1@lemmy.ml
              link
              fedilink
              arrow-up
              8
              arrow-down
              1
              ·
              1 year ago

              Because Pipewire only handles and understands media streams, so it can stream the output of a window or the whole desktop, but only because the Wayland compositor has already composed the windows and other data it gets from the application to a visual and hands the final result to Pipewire.

              • uis@lemmy.world
                link
                fedilink
                arrow-up
                1
                arrow-down
                1
                ·
                1 year ago

                Which goes back to oroginal question. Why pipewire if there are already wayland extensions?

                • Ullebe1@lemmy.ml
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  1 year ago

                  Because it is convenient for programs to use Pipewire for screensharing, as those programs can then also use the same Pipewire support for all their audio and webcam needs. Also Pipewire is good at multiplexing the various media streams.

                  • uis@lemmy.world
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    edit-2
                    1 year ago

                    And what developers will hammer their apps to one sound server implementation? What is convenient here? Loosing interoperability? You always can use Wayland for screensharing, ALSA for sound and V4L2 for webcam.

    • eksb@programming.dev
      link
      fedilink
      English
      arrow-up
      19
      ·
      1 year ago

      I started running OBS with a virtual camera to do screen sharing. It is so much nicer to manage sharing with OBS than with Slack/Google Meet/Discord.

      • RiotRick@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        Oh, that sounds like an interesting idea. Currently stuck with teams at work. Screen sharing does work under wayland. But definitely going to try this.

      • russjr08@outpost.zeuslink.net
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I’m not sure why, but every time I use XWayland Video Bridge (installed as of about 2 days ago so it should still be pretty new), I just end up with a black screen being broadcasted - not sure what could be causing that.