Since remote-desktop-desktop (the Wayland screen sharing option) does not (yet) work in Gentoo, vino is (currently) the only option to share a screen in Gentoo+gnome. In contrast to the statement here: https://wiki.gentoo.org/wiki/Project:GNOME/3.36-notes, vino does NOT actually work, even in an xorg session, when net-misc/vino is explicitly merged. The reason is that upstream has indiscriminately disabled vino: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/a93df952 It is relatively straightforward to undo this commit, at least until the wayland option works. Ubuntu have already done it: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871787 The patch in question, which I have attached to this issue, works fine in Gentoo: after applying it, the "Screen Sharing" option in the Gnome settings is once again available and functional, just as it was in all previous versions of Gnome. Reproducible: Always Steps to Reproduce: 1. install gnome-base/gnome-settings-daemon-3.36.1 2. install net-misc/vino-3.22.0-r3 3. start an Xorg (not a Wayland) gnome session (e.g. by selecting "GNOME Xorg") among the available sessions in gdm, or by merging with USE="-wayland") Actual Results: In the gnome settings app, Sharing tab, "Screen Sharing" will appear, but will be inoperable (the activation toggle is inactive). Expected Results: In the gnome settings app, Sharing tab, "Screen Sharing" should appear, AND be activatable, as it always was in previous gnome versions.
Created attachment 680542 [details, diff] undo for upstream commit https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/a93df952
oh, I knew 3.36.5 did that in gnome-control-center with this NEWS item: - Replace vino with gnome-remote-desktop for X11 sessions. But apparently you found something that did it earlier at gnome-settings-daemon level then. I think at this point the solution from my POV is to just move to gnome-remote-desktop and figure out the remaining things for that to become the default for us. As in, if I have time to work on this topic, that's the route I would take. That said, maybe someone else on the team can put that in meanwhile, and perhaps bump gnome-control-center to 3.36.5 while reverting that ones vino removal for the time being (because it also contains an important runtime fix for application panel some of our users are suffering).
vino is gone from the tree now.
