cosmic vinagre can't connect to disco vino-server

[Jonathan Kamens]

After upgrading from my desktop cosmic to disco and rebooting, my cosmic laptop can no longer connect to vino-server on my disco desktop. Vino-server logs:

Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM [IPv4] Got connection from client jik5.kamens.us
Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM other clients:
Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM Client Protocol Version 3.7
Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM Advertising security type 18
Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM Client returned security type 18
Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM TLS Handshake failed: The TLS connection was non-properly terminated.
Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM Client jik5.kamens.us gone
Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM Statistics:
Jan 22 11:01:32 jik5 vino-server[4478]: 22/01/2019 11:01:32 AM framebuffer updates 0, rectangles 0, bytes 0

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: vino 3.22.0-4ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 22 11:02:49 2019
InstallationDate: Installed on 2019-01-02 (20 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: vino
UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

[Jonathan Kamens (jik)]

I've since upgraded my laptop to disco, and it _can_ connect to my home machine, so either (a) the problem with vino in disco has been fixed, or (b) vinagre on disco can connect to vino on disco but vinagre on cosmic still can't. I'm not sure which.

[Sebastien Bacher (seb128)]

Thank you for your bug report. Connecting a cosmic machine to a disco one works fine here. Do you still have the journal log from the client, does that include any error? Did you get an error dialog/what was it saying exactly?

[Jonathan Kamens (jik)]

There were no errors anywhere I could find on the client.

[Jonathan Kamens (jik)]

It just said "Connection closed" when I tried to connect.

I just checked journalctl and here's what I see on the day I reported this issue for vinagre:

```
Jan 22 11:01:32 jik-x1 vinagre[21144]: Theme parsing error: <data>:2:28: The style property GtkButton:default-border is deprecated and shouldn't be used anymore. It will be removed in a future version
Jan 22 11:01:32 jik-x1 vinagre[21144]: Theme parsing error: <data>:3:36: The style property GtkButton:default-outside-border is deprecated and shouldn't be used anymore. It will be removed in a future version
Jan 22 11:01:32 jik-x1 vinagre[21144]: Theme parsing error: <data>:4:25: The style property GtkButton:inner-border is deprecated and shouldn't be used anymore. It will be removed in a future version
Jan 22 11:01:32 jik-x1 vinagre[21144]: Theme parsing error: <data>:5:30: The style property GtkWidget:focus-line-width is deprecated and shouldn't be used anymore. It will be removed in a future version
Jan 22 11:01:32 jik-x1 vinagre[21144]: Theme parsing error: <data>:6:27: The style property GtkWidget:focus-padding is deprecated and shouldn't be used anymore. It will be removed in a future version
Jan 22 11:01:32 jik-x1 vinagre[21144]: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner ViewAutoDrawer)
```

None of these seems relevant. The last error you see there has been logged by vinagre forever and is not new.

[Sebastien Bacher (seb128)]

Ok, let's close the bug then since it works now and we can't do much fixing without more debug info. Feel free to reopen if you manage to get into the buggy state again