id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
12655	Replace Vino (unmaintained) with gnome-remote-desktop	Douglas R. Reno	Douglas R. Reno	"As part of my trip through the GNOME section to do package updates, I took a look at Vino since I used to build it prior to building gnome-control-center (that's for the Sharing Panel - and is the only VNC server that was/is Wayland compatible). I've discovered that the last technical commit to Vino was several years ago, only receiving translation updates since. No bug reports/issues have been solved, and no bugs were carried over from their Bugzilla transition. In addition, it was marked as ""removed"" from the moduleset for 3.34.1.

I'd like to propose replacing it with what seems to be it's replacement... gnome-remote-desktop:

https://gitlab.gnome.org/jadahl/gnome-remote-desktop

The latest release, 0.1.7, can be found here (it hasn't made it to the GNOME mainline/FTP...):

[https://gitlab.gnome.org/jadahl/gnome-remote-desktop/uploads/ed3e8b8ebc1a74b6f4ed7260a2739f40/gnome-remote-desktop-0.1.7.tar.xz]

This feature was previously part of Mutter-3.26 (experimental), and then split off in 3.30 to this project it seems.

It's only non-book dependency is libvncserver:

[https://libvnc.github.io/]

Both of these seem simple in terms of instructions. gnome-remote-desktop is meson/ninja/ninja install, and libvncserver seems to be CMake/Make/Make Install (although I suppose we could have it generate ninja compatible files instead).

I propose adding gnome-remote-desktop in GNOME Applications, and adding dependencies on it to gnome-control-center (optional)."	task	closed	normal	9.1	BOOK	SVN	medium	wontfix