4 ms·

Agreed. Tried Wayland again last year. Screen sharing in Electron doesn't work, so can't share screen in Slack. Googled, known issue. I don't care how much

by axaxs 6y ago

Agreed. Tried Wayland again last year. Screen sharing in Electron doesn't work, so can't share screen in Slack. Googled, known issue. I don't care how much better Wayland is...if it can't do something I'm used to and need, it's going in the trash. I don't have time or interest to read mailing lists and bug trackers to know when it's fixed.

away_throw 6y ago
I believe that this is being fixed soon if you compile Electron with "Ozone" support. Otherwise, I use the current workaround of using OBS with a "virtual webcam" which allows me to stream OBS to a webcam and just use my webcam as the screenshare. Actually ends up working better than any screenshare utility that I've used.
- axaxs 6y ago
  This doesn't seem as straightforward as 'click the screenshare button to share your screen', which is how it works in xorg mode. Editing since I can't reply - I didn't mean to come across as rude, sorry for that. Just explaining that as a user, it doesn't work out of the box. Having to explain to users to do the above is not an ideal solution.
  - away_throw 6y ago
    That's true. Hopefully Ozone will be officially released in Chromium/Electron which will make this as simple as that. At least in Discord, XOrg screenshare always gave me trouble.
    - aeroevan 6y ago
      There's also pipewire which doesn't depend on ozone, but is optional I guess. What's even worse, slack doesn't allow sharing from chrome which just works for MS Teams via pipewire.
senko 6y ago
... sounds like you should complain to Slack?
vetinari 6y ago
So Slack didn't bother building with `rtc_use_pipewire=true` and that's Wayland's problem? Complain to Slack.
- rcxdude 6y ago
  Support from popular apps absolutely is a problem for the platform. It might not be caused by them, but it is their problem. The user doesn't care who's fault it is, they're just going to go with the combination which works for them.
  - vetinari 6y ago
    While I agree, that support for popular apps is a problem for platform, it doesn't mean that the platform will freeze for every snowflake app. Apple for example regularly uses pressure from users on app authors to drive improvements in their platform. I don't see why Linux distributions should flip backward to keep their platform static, to the detriment of their long term development.
- zamadatix 6y ago
  Pipewire is still 0.x as of today, let alone when they last tried it, so I don't think anybody should be going to Slack like they were too lazy to build it "right". Besides even if it was built with that the screensharing via pipewire isn't at feature parity with normal screen/monitor/window level sharing so it's not a 1:1 drop in quite yet. Wayland said screen sharing is something to be solved outside of Wayland itself. That solution is still early and not complete. It's not anybody's problem, it's just how things are. It'll get fixed eventually, in the meantime X11 still runs fine for most users and in 6-12 months switching to Wayland should have fewer tradeoffs. Until then Wayland is missing some use cases X11 easy fulfills. Unfortunately X11 is also missing many use cases Wayland fills. As a result we should expect different users to be better served by different answers about how ready a Wayland environment is for them and both to be equally correct.
  - vetinari 6y ago
    Yes, Pipewire is at 0.3 today; but that's not a problem. Pipewire has the ambition to replace Pulseaudio, Jack and provide APIs for several other subject, not just screen grabbing. That's the part that is missing toward 1.0. Screengrabbing during the last year was even better than what X11 could provide, including the ability for the user to limit the grabbing to display or window. That's something that user cannot have under control in X11. Pipewire is also not limited to Wayland; it will work with X11 too, so the X11 users won't be abandoned just because there's Wayland support too. Firefox doesn't seem to have problem with it, Chrome has it behind flags. For apps with fast moving releases as these, I don't see any problem with them supporting 0.3 release and when/if there is API breaks, updating it. Beats not supporting screen sharing under Wayland at all.

by axaxs 6y ago

away_throw 6y ago

I believe that this is being fixed soon if you compile Electron with "Ozone" support. Otherwise, I use the current workaround of using OBS with a "virtual webcam" which allows me to stream OBS to a webcam and just use my webcam as the screenshare. Actually ends up working better than any screenshare utility that I've used.

axaxs 6y ago
This doesn't seem as straightforward as 'click the screenshare button to share your screen', which is how it works in xorg mode. Editing since I can't reply - I didn't mean to come across as rude, sorry for that. Just explaining that as a user, it doesn't work out of the box. Having to explain to users to do the above is not an ideal solution.
- away_throw 6y ago
  That's true. Hopefully Ozone will be officially released in Chromium/Electron which will make this as simple as that. At least in Discord, XOrg screenshare always gave me trouble.
  - aeroevan 6y ago
    There's also pipewire which doesn't depend on ozone, but is optional I guess. What's even worse, slack doesn't allow sharing from chrome which just works for MS Teams via pipewire.

senko 6y ago

... sounds like you should complain to Slack?

vetinari 6y ago

So Slack didn't bother building with `rtc_use_pipewire=true` and that's Wayland's problem? Complain to Slack.

rcxdude 6y ago
Support from popular apps absolutely is a problem for the platform. It might not be caused by them, but it is their problem. The user doesn't care who's fault it is, they're just going to go with the combination which works for them.
- vetinari 6y ago
  While I agree, that support for popular apps is a problem for platform, it doesn't mean that the platform will freeze for every snowflake app. Apple for example regularly uses pressure from users on app authors to drive improvements in their platform. I don't see why Linux distributions should flip backward to keep their platform static, to the detriment of their long term development.
zamadatix 6y ago
Pipewire is still 0.x as of today, let alone when they last tried it, so I don't think anybody should be going to Slack like they were too lazy to build it "right". Besides even if it was built with that the screensharing via pipewire isn't at feature parity with normal screen/monitor/window level sharing so it's not a 1:1 drop in quite yet. Wayland said screen sharing is something to be solved outside of Wayland itself. That solution is still early and not complete. It's not anybody's problem, it's just how things are. It'll get fixed eventually, in the meantime X11 still runs fine for most users and in 6-12 months switching to Wayland should have fewer tradeoffs. Until then Wayland is missing some use cases X11 easy fulfills. Unfortunately X11 is also missing many use cases Wayland fills. As a result we should expect different users to be better served by different answers about how ready a Wayland environment is for them and both to be equally correct.
- vetinari 6y ago
  Yes, Pipewire is at 0.3 today; but that's not a problem. Pipewire has the ambition to replace Pulseaudio, Jack and provide APIs for several other subject, not just screen grabbing. That's the part that is missing toward 1.0. Screengrabbing during the last year was even better than what X11 could provide, including the ability for the user to limit the grabbing to display or window. That's something that user cannot have under control in X11. Pipewire is also not limited to Wayland; it will work with X11 too, so the X11 users won't be abandoned just because there's Wayland support too. Firefox doesn't seem to have problem with it, Chrome has it behind flags. For apps with fast moving releases as these, I don't see any problem with them supporting 0.3 release and when/if there is API breaks, updating it. Beats not supporting screen sharing under Wayland at all.