Bug 1392072 - Screen casting (Bluejeans / WebEx / etc) does not work when running Wayland
Summary: Screen casting (Bluejeans / WebEx / etc) does not work when running Wayland
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 34
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-04 17:58 UTC by Mike
Modified: 2022-06-07 21:11 UTC (History)
60 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 21:11:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot of bluejeans streaming screen (64.97 KB, image/png)
2019-06-13 14:44 UTC, Alberto Fanjul Alonso
no flags Details

Description Mike 2016-11-04 17:58:58 UTC
Description of problem:
When running Bluejeans on Fedora 24 with Wayland, when you "share" your screen the others on the webcast only see a black screen.

Version-Release number of selected component (if applicable):


How reproducible: Easily


Steps to Reproduce:
1. Log into Fedora 24 using Wayland
2. Start Bluejeans with a second person to see your screen
3. Try to share your screen.  The other person only sees a black screen.

Actual results:
Black screen is shared

Expected results:
Actual screen is shared

Additional info:
It seems that Wayland does not use the same methods for screen sharing application to be able to share out your screen.

Comment 1 Larry O'Leary 2016-12-19 19:31:50 UTC
Same applies to Fedora 25. 

It is interesting that the mouse cursor is visible. Also, when using the BlueJeans browser plug-in, it is possible to share individual application windows. But again, not possible to share a screen/desktop.

Switching to XServer fixes this.

Comment 2 Barnaby Court 2017-01-19 17:09:04 UTC
When using BlueJeans it is dependent on the application. For example, Sharing Chrome works but you can not share Gnome Terminal. The terminal app doesn't even show up in the list of available applications to share.

Comment 3 Barnaby Court 2017-01-19 17:09:50 UTC
Oops, I forgot to give version information. I am using Fedora 25.

Comment 4 Carlos 2017-01-19 21:09:53 UTC
Same happening here. Also running Fedora 25

Comment 5 Avin Zhang 2017-01-23 01:32:38 UTC
Same here,  I'm also using F25

Comment 6 Karl Stevens 2017-01-29 07:25:32 UTC
I see the same symptoms.  Also on Fedora 25.  Is this something that's likely fixable in the near future, or do we need to go back to X for now if we want to webcast?

Comment 7 Carlos 2017-02-13 13:00:39 UTC
Looks like Hangouts has the same issue while trying to screenshare the whole screen. However, it gives the chance to share a particular window successfully. May this last approach be feasible to implement? Same as how the Windows and Mac BlueJeans app work.

Thanks!

Comment 8 Adam Chasen 2017-06-14 13:20:46 UTC
This is promising. Looks like there is something upstream already which shares a full screen in a very specific way, but they mention serious security concerns: https://cgit.freedesktop.org/wayland/weston/commit/?id=47928d8715038e7a5fd7fd383dc3ec2c185ddd23

Definitely a different mechanism than all of these solutions use today (X11 libs, gstreamer, etc.) to grab window contents. Ideally, there could be a mechanism to re-use the existing X11 capture pathways without having to load up into Xorg (which I just started doing after a year of struggling with screen sharing on Wayland).

Comment 9 Fedora End Of Life 2017-07-25 23:46:17 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 10 Marina Kalinin 2017-07-26 16:53:03 UTC
Hi Adam,

Do you have any estimate when this can be fixed please?
The current workaround would be to switch to gnome+Xorg, however, what if in the next release this would not be available. Bluejeans and webex are widely used tools in the enterprise and we should get this fix at some point please.

Thanks,
Marina.

Comment 11 Carlos 2017-07-26 17:23:17 UTC
@Bill @Adam

The issue is also reproducible on 25 and 26. We need this asap, as Marina said, this will stop working soon.

Thanks

Comment 12 Waldirio M Pinheiro 2017-10-31 18:51:38 UTC
Hello all

I'm facing the same issue using Fedora 26.

Appreciate any feedback.

Best Regards
-- 
Waldirio M Pinheiro | Senior Software Maintenance Engineer

Comment 13 Marcos Amorim 2017-12-08 13:39:51 UTC
Hello All, 

I solved the problem change to Xorg and Gnome, on your login screen you need to click on icon and change to "Gnome & Xorg". works fine in my case.

Best,

Comment 14 Marcos Amorim 2017-12-10 12:22:14 UTC
(In reply to Marcos Amorim from comment #13)
> Hello All, 
> 
> I solved the problem change to Xorg and Gnome, on your login screen you need
> to click on icon and change to "Gnome & Xorg". works fine in my case.
> 
> Best,

Sorry, I forget my environment, I'm using Fedora 26 ;-)

Comment 15 Yajo 2017-12-11 08:49:29 UTC
Thanks Marcos, but remember that's just a workaround. The problem of Wayland not allowing screen sharing is still there. You just stop using Wayland with that trick, and that's what everyone has to do nowadays, but if Wayland wants to replace Xorg, it still needs to fix this.

Comment 16 Dave Neary 2017-12-20 15:16:52 UTC
I also have this issue on Fedora 26. When I try to share a specific application window, I do not see evince or LibreOffice windows in the sharable windows, and if I share the screen when one of these applications are in the foreground. As a result, I cannot share presentations on Bluejeans since updating to Fedora 26.

Comment 17 Matteo Mortari 2018-01-08 13:02:47 UTC
I have the same issue on Fedora 27; I am a Bluejeans user.

I agree with Marina ref. https://bugzilla.redhat.com/show_bug.cgi?id=1392072#c10

I worked around as suggested by Marcos https://bugzilla.redhat.com/show_bug.cgi?id=1392072#c13

Comment 18 Geoffrey De Smet 2018-02-19 09:30:04 UTC
I have th same issue on Fedora 27. This is really annoying.

Comment 19 Ivan K 2018-06-27 15:25:55 UTC
Fedora 27 with latest updates - still the issue.

Comment 20 Buvanesh Kumar 2018-07-08 04:15:30 UTC
Fedora 28 also having this same issue

Comment 21 Tom George 2018-10-23 13:32:45 UTC
(In reply to Ivan K from comment #19)
> Fedora 27 with latest updates - still the issue.

+1, still seeing this issue.

Comment 22 Adam Chasen 2018-10-24 17:57:51 UTC
I am not sure which API zoom.us uses, but it is capable of screencasting (no individual windows, only the entire desktop).

Comment 23 Lukas Svaty 2018-10-31 08:58:59 UTC
F28, still relevant

Comment 24 Juraci Paixão Kröhling 2018-11-16 11:54:24 UTC
F29 and it still doesn't work.

Comment 25 Ben Cotton 2018-11-27 13:33:34 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 26 Dave Neary 2018-11-27 14:49:05 UTC
Updating version for this issue. This affects a lot of people who are trying to use Fedora for daily usage and who use BlueJeans as the videoconferencing software at their employers. How do I know if this has been looked at by a relevant developer? Is there a team or maintainer I should CC? At this point it's been open since Fedora 24 (2 years), with multiple comments from users, but no feedback from the Wayland developers.

Comment 27 Alberto Fanjul Alonso 2019-06-13 14:44:05 UTC
Created attachment 1580331 [details]
screenshot of bluejeans streaming screen

Comment 28 Alberto Fanjul Alonso 2019-06-13 14:45:07 UTC
Just in case this is still hitting you. Screen sharing with wayland:

-Enable pipewire:
   systemctl --user enable pipewire
   systemctl --user start pipewire

- Desktop https://wiki.gnome.org/Projects/Mutter/RemoteDesktop …
   python3 http://gnome-screen-cast.py 

- chrome:
   chrome://flags/#enable-webrtc-pipewire-capturer (enabled)

Enjoy! (screenshot attached of bluejeans streaming screen)

Comment 29 Hongkai Liu 2019-06-13 16:33:53 UTC
thanks Alberto.
Tried with Fedora30 and chrome.
It works nicely.

Comment 30 Larry O'Leary 2019-06-13 17:50:28 UTC
Thanks Alberto. The provided workaround does work. However, once applied I can no longer share individual applications. 

So it seems:

* With the workaround I can share my entire screen/desktop but no individual applications.
* Without the workaround I can share individual applications but not my entire screen/desktop.

Painful trade-off but I mostly need to share my entire screen so this is good. Thanks again!

Comment 31 Alberto Fanjul Alonso 2019-06-13 19:27:24 UTC
I can confirm. chrome://flags/#enable-webrtc-pipewire-capturer has this regression. 

I just turn it to default again (I suppose default is disabled) and I can see again applications, but no screen.

Comment 32 Alberto Fanjul Alonso 2019-06-14 14:32:37 UTC
Big TODO: share individual apps is still (at the time writing) not implemented:

https://github.com/flatpak/xdg-desktop-portal-gtk/issues/204

Comment 33 Charles Haithcock 2019-07-04 20:16:30 UTC
Kicking the prio and sev to urgent. Dave Neary said it best as to why it is as such, as Red Hat is also one of these companies.

Comment 34 Alberto Fanjul Alonso 2019-07-05 08:19:15 UTC
Charles Haithcock not sure if you check it, but this is just about correctly setup your system.

What is urgent here?

Comment 35 Charles Haithcock 2019-08-06 00:23:27 UTC
(In reply to Alberto Fanjul Alonso from comment #34)
> Charles Haithcock not sure if you check it, but this is just about correctly
> setup your system.

Thank you for this, but from my understanding the history of this BZ, the problem of properly sharing both the desktop or individual apps seems to be something not yet done? In chromium for example, they implemented an experimental flag enabling PipeWire support in WebRTC. That being said, like the workaround above, it seems you can only do either the entire desktop (which is still black only) or the screens and not specific applications. And currently, if an application does use pipewire, it seems those applications can not select specific applications to share. The full workaround seems to be using Xorg, which is contradictory to what I interpret as the future of fedora's desktop (moving to wayland). 

Admittedly, I don't muck with userspace much and predominantly work within the kernel so I may not completely understand what is going on. My understanding of the state of this BZ was that some components were not completely implemented yet in wayland and the components that are there need to have their respective application counterparts implemented in the individual applications that want to run wayland (e.g. chromium's pipewire support in WebRTC). 

The main reasons behind increasing the severity are that RHEL 8 is shipping with wayland as the default (meaning even more eyes on the potential issue) and the bz hadn't had much activity until a bit more recently. 

Anything I can help test out?

Comment 36 Alberto Fanjul Alonso 2019-08-06 07:45:35 UTC
Share specific windows was, simply still not implemented.

I'm actively workin on it: https://github.com/flatpak/xdg-desktop-portal-gtk/pull/217 and right now code works, just need more polish (run async and the like)

Hoppe to land it soon

Comment 37 Charles Haithcock 2019-08-06 20:22:39 UTC
(In reply to Alberto Fanjul Alonso from comment #36)
> Share specific windows was, simply still not implemented.
> 
> I'm actively workin on it:


Fantastic! That's great to hear. Looking forward to updates on this. Thanks!

Comment 38 Ben Cotton 2019-10-31 18:44:55 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 39 J. Alexander Jacocks 2019-10-31 19:09:22 UTC
I just re-tagged this for F30, since the problem continues there, and I don't want this bug to be lost with F29's EOL.

Comment 40 Alberto Fanjul Alonso 2019-11-04 08:17:19 UTC
The desktop side is landed (screen and windows sharing) https://github.com/flatpak/xdg-desktop-portal-gtk/pull/225 (merged)

The navigator side (for chrome) is simplified to avoid a dialog hell. https://twitter.com/JanGrulich/status/1189922704419373057?s=20

Don't know the timeline for Fedora, bus I guess F31 have this fixed https://fedoramagazine.org/announcing-fedora-31/, so I would open bugs for fedora, to know if this will be backported to old releases.

Comment 41 Ben Cotton 2020-04-30 20:14:59 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 42 Naveen Malik 2020-05-06 19:28:16 UTC
Still a problem on Fedora 31 it appears.

Comment 43 Ben Cotton 2020-05-26 14:32:06 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 44 Larry O'Leary 2020-05-26 15:06:07 UTC
Looks like we failed to change the version to Fedora 31.

Reopening as this is still present.

Comment 45 Tanay Shah 2020-06-26 16:55:12 UTC
The same issue still persists. Can not share gnome-shell in fedora 31

Comment 46 Ben Cotton 2020-11-03 17:16:58 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 47 Ben Cotton 2020-11-24 19:13:00 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 48 Dana Walker 2021-07-20 20:05:38 UTC
I am experiencing this issue on Fedora 34.  Just did laptop refresh, and the new laptop has a clean Fedora 34 install with Gnome version 40.1.0 with Wayland.  Tried to do a screenshare in Chrome, only black screen when trying to do whole screen and window or tab did not show my terminal as an option nor firefox windows, swapped to Firefox, only black screen again, but there was another option to select with operating system and the browser dropdown let me select screen and it worked.  However, once clicking stop presenting, I then lost audio.  All other participants could hear me and each other, but I could not hear them.  Will try to use something other than Wayland for now to work around this, but wanted to pass along that this is indeed still an issue on more recent versions of Fedora.

@bcotton

Comment 49 John Call 2021-07-21 21:52:07 UTC
Dana, I find that on new installs of Fedora I still have to enable Pipewire in my user session and toggle a flag in Chrome before I can successfully screenshare. From comment #28, I run these two commands...

-Start and enable pipewire:
   systemctl --user enable pipewire --now


-Configure Chrome to allow pipewire capture (paste the URL below into your chrome browser):
   chrome://flags/#enable-webrtc-pipewire-capturer (enabled)

Comment 50 Dana Walker 2021-07-22 15:53:01 UTC
Tried that, appears to be still broken for me.  I'm going to try not using Wayland.  Just wanted it reported that the issue does indeed still exist.  Thanks!

Comment 51 Eduardo Habkost 2021-07-22 20:36:54 UTC
(In reply to John Call from comment #49)
> -Configure Chrome to allow pipewire capture (paste the URL below into your
> chrome browser):
>    chrome://flags/#enable-webrtc-pipewire-capturer (enabled)

The workaround helped, but the behaviour of Google Chrome is weird when enabling this flag.  I'm documenting it here just for reference:

If I ask Google Meet to share a window, I see the system Screen Share dialog.  If I select a window at the dialog, the "Share an application window" dialog on Chrome is empty and the "Share" button is greyed out.  I can't share a window this way.

If I ask Google Meet to share the entire screen, the system Screen Share dialog appears twice in a row.  Except for that, the option I choose at the system dialog (either single window or entire screen) works as expected.

I'm running Google Chrome "Version 91.0.4472.164 (Official Build) (64-bit)".

Comment 52 Jonas Ådahl 2021-07-23 09:40:25 UTC
The multiple dialogs and Chromes inability to system dialogs for sharing sensitive resources is a known issue. The former is related to WebRTC, and the latter Chrome.

Comment 53 Ben Cotton 2022-05-12 15:13:45 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 54 Vít Ondruch 2022-05-16 12:43:31 UTC
Just FTR, for FF, there is bug 2070556, which provides more details and suggest improvements for FF to help better debug the screen sharing issues. There was also this [1] workstation WG ticket addressing more possible issues leading to non working screen casting.


[1]: https://pagure.io/fedora-workstation/issue/298

Comment 55 Ben Cotton 2022-06-07 21:11:20 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.