7 ms·

Some friends had significant issues with screen sharing on Wayland on Arch. Pipewire wouldn't work correctly, or only allow sharing one screen, but not another.

Some friends had significant issues with screen sharing on Wayland on Arch. Pipewire wouldn't work correctly, or only allow sharing one screen, but not another. As far as I can tell, they have resolved these issues now, but it was a pain point.

beermonster 5y ago
Pipewire itself has had some issues as it’s still relatively new. But I’ve found the last few releases have ironed them out. bleeding edge is more the issue than Arch
- Cu3PO42 5y ago
  I agree it's related to maturity, but on the other hand Pipewire was working just fine for me on Fedora without further setup. I understand they're different distros with different philosophies, but in the end I do need my screen sharing to work no questions asked.
  - beermonster 5y ago
    Fedora do seem [1] to make the same versions available. So there doesn't seem to be any' holding back' of unstable versions unless they decide to backport fixes from higher versions? Fedora do work on six-month releases so there will be some version jumps between versions of Fedora but IIRC they will update little and often just like Arch whilst on a given release. https://koji.fedoraproject.org/koji/packageinfo?packageID=24555 https://koji.fedoraproject.org/koji/packageinfo?packageID=24...
    - Cu3PO42 5y ago
      I'm personally guessing it's not as much that the releases themselves were inherently buggy as much as some configuration was required to get it working correctly. And Fedora shipped some configuration that worked for the standard environment you'd have when you just installed Fedora and didn't change things around too much. Since Arch encourages you to build your own setup and roll your own configs to a much larger degree, the defaults probably weren't quite right or quite enough for their specific setups. I don't mean this in an "Arch bad, other distro good" sense, I just wanted to say I've seen the same thing where some detail in an Arch setup was broken. It's simply different strokes for different folks.
- jatone 5y ago
  i mean.... pipewire issues are the end users fault, it is opt in. if you're using pipewire you chose to use unstable beta software.

beermonster 5y ago

Pipewire itself has had some issues as it’s still relatively new. But I’ve found the last few releases have ironed them out. bleeding edge is more the issue than Arch

Cu3PO42 5y ago
I agree it's related to maturity, but on the other hand Pipewire was working just fine for me on Fedora without further setup. I understand they're different distros with different philosophies, but in the end I do need my screen sharing to work no questions asked.
- beermonster 5y ago
  Fedora do seem [1] to make the same versions available. So there doesn't seem to be any' holding back' of unstable versions unless they decide to backport fixes from higher versions? Fedora do work on six-month releases so there will be some version jumps between versions of Fedora but IIRC they will update little and often just like Arch whilst on a given release. https://koji.fedoraproject.org/koji/packageinfo?packageID=24555 https://koji.fedoraproject.org/koji/packageinfo?packageID=24...
  - Cu3PO42 5y ago
    I'm personally guessing it's not as much that the releases themselves were inherently buggy as much as some configuration was required to get it working correctly. And Fedora shipped some configuration that worked for the standard environment you'd have when you just installed Fedora and didn't change things around too much. Since Arch encourages you to build your own setup and roll your own configs to a much larger degree, the defaults probably weren't quite right or quite enough for their specific setups. I don't mean this in an "Arch bad, other distro good" sense, I just wanted to say I've seen the same thing where some detail in an Arch setup was broken. It's simply different strokes for different folks.
jatone 5y ago
i mean.... pipewire issues are the end users fault, it is opt in. if you're using pipewire you chose to use unstable beta software.