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 …

  • luciferofastora@lemmy.zip
    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
      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@lemmy.zip
        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