Summary: | gnome-base/gnome-settings-daemon-3.36.1 deliberately disables vino, even in xorg | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | James Bates <james.h.bates> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | undo for upstream commit https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/a93df952 |
Description
James Bates
2021-01-01 20:20:46 UTC
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. |