GNOME Bugzilla – Bug 637827
vino crashes with > 1 screen
Last modified: 2020-11-12 13:55:16 UTC
As has been documented downstream in https://bugs.launchpad.net/ubuntu/+source/vino/+bug/682578, the vino server crashes when there is more than one screen on the machine, as returned by gdk_display_get_n_screens(). It seems it crashes because it tries to open the same port twice.
I do not think it tries to open one port twice. the log shows it listening on two different ports. Running Gentoo, used vino-2.28.2, accessed one screen only, never tried the other. After upgrade to vino-2.32.2, it fails to register GObject with DBusConnection: 09/06/2011 10:48:17 Listening IPv6://[::]:5900 09/06/2011 10:48:17 Listening IPv4://0.0.0.0:5900 09/06/2011 10:48:17 Autoprobing selected port 5900 09/06/2011 10:48:17 Advertising security type: 'TLS' (18) 09/06/2011 10:48:17 Advertising authentication type: 'No Authentication' (1) 09/06/2011 10:48:17 Advertising security type: 'No Authentication' (1) 09/06/2011 10:48:17 Autoprobing TCP port in (all) network interface 09/06/2011 10:48:17 Listening IPv6://[::]:5900 09/06/2011 10:48:17 Listening IPv4://0.0.0.0:5900 09/06/2011 10:48:17 Problems in NewSocketListenTCP() 09/06/2011 10:48:17 Listening IPv6://[::]:5901 09/06/2011 10:48:17 Listening IPv4://0.0.0.0:5901 09/06/2011 10:48:17 Autoprobing selected port 5901 09/06/2011 10:48:17 Advertising security type: 'TLS' (18) 09/06/2011 10:48:17 Advertising authentication type: 'No Authentication' (1) 09/06/2011 10:48:17 Advertising security type: 'No Authentication' (1) ** ERROR **: Failed to register GObject with DBusConnection
Really? Nothing? Not even a triage of this issue? It's been open nearly 8 months now.
I do not use multiple X screens, so this bug report could be difficult for me to reproduce. However, the root cause seems to be trying to register a D-Bus object twice. There are likely assumptions made by Vino that are not valid when two X screens are used. Assuming that there is only one X screen could be a workaround, but it is probably better to come up with a fic instead. In Vino 3.0.0, the D-Bus handling was rewritten by Ryan Lortie to use GDBus, so this bug might be fixed in that or newer versions. Please test that, and if there is still a problem, please provide a stack trace (with debug symbols, as described at http://live.gnome.org/GettingTraces) of the crash.
The problem with trying to use Vino 3.0.0 is that that likely requires Gnome 3.0, yes? I am not using Gnome 3.0 (and likely won't be for some time, if at all -- it will depend on whether the shortcomings are addressed in future versions or not) due to it's numerous short-comings (compared to Gnome 2.32 for example). I'd really like to see this fixed in Vino 2.32.x since that's that last available version for a usable Gnome.
+ Trace 228043
It seems that the Vino debug symbols are missing from the stack trace, although I can see that the crash occurs after connection to Telepathy. Please install the necessary debug symbols and post an updated trace. Vino 3.0.3 requires GTK+ 3, for GtkApplication and the preferences dialog, but otherwise nothing particularly tied to GNOME 3.0. AS GTK+ 3 can be installed in parallel with GTK+ 2, it is relatively simple to use Vino 3 on a predominantly GTK+ 2 system.
Ahhh. Sorry 'bout that. This one should have them, and the libtelepathy-glib0 symbols for good measure.
+ Trace 228044
Vino is not under active development anymore and unmaintained. Please use gnome-remote-desktop instead. Closing this report as WONTFIX to reflect reality.
Created attachment 374303 [details] gnome-remote-desktop repeating keystrokes
Only 10 years after opening this ticket, however... (In reply to André Klapper from comment #7) > Vino is not under active development anymore and unmaintained. > > Please use gnome-remote-desktop instead. Does that work with Xorg? Wayland is an non-starter for any number of reasons. No soft-kvm is one: https://github.com/debauchee/barrier/issues/109 But the main one is really that gnome-remote-desktop and pipewire performance sucks. Really badly: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/32 https://www.reddit.com/r/gnome/comments/hr5gme/gnomeremotedesktop_absolutely_hammers_my_cpu/ And that's when it somewhat works. As of late, I only ever seem to get a black screen from it. I also often suffer multiple keystroke sends. That's where I press a key once but it gets received numerous times. See the attachment https://bug637827.bugzilla-attachments.gnome.org/attachment.cgi?id=374303.
This ticket is about vino, it is not about gnome-remote-desktop. Please ask general questions in a support forum. Thanks for your understanding.
Yes, and my response was about vino. Specifically if vino has been discontinued before it's replacement is actually up to the task of, well, actually replacing it. And you didn't even answer the first question. Does gnome-remote-desktop work with Xorg, as vino did. See it's still about vino.
Yes, as this is not a place for general questions but an issue tracker. See my previous comment.
I am a messenger. I am not a gnome-remote-desktop developer who might not want to waste years working around the limitations of the ancient Xorg architecture. Nobody can stop you from continuing to use Vino with all its security issues and limitations; I merely communicated that Vino will not see any further development. Thanks for understanding that. :)