Bug#762691: vino: Latest vino update broke gnome-session

[Andreas Henriksson]

Hello Kai Lüke

Thanks for your followup!

Hello,
I also encountered this problem while running 3.14 whereever possible.
gnome-session[23651]: GLib-GIO-ERROR: Settings schema 'org.gnome.Vino'
does not contain a key named 'enabled'
aborting...

[...]

So either the schema org.gnome.Vino is wrong or gnome-session looking
for that key and this is why the error message is brought up. And
because this is an error message, g_logv will just kill the whole
process, I guess by reading the docs on g_logv: " If the log level has
been set as fatal, the abort() function is called to terminate the
program."
(https://developer.gnome.org/glib/stable/glib-Message-Logging.html)

Some more details from my side might be in place here.

The org.gnome.Vino schema dropped the "enabled" key in vino v3.14.0
(some time during 3.13.x to be more exact).

There are supposed to be no users of this in gnome 3.14.0.

(gnome-control-center 3.12.x used the key and I've already added an
appropriate Breaks in vino for it in the pkg-gnome vcs so it'll be part
of next upload.)

I've searched gnome-session but it (as far as I could find) doesn't use
this key. I suspect something else is hooking into gnome-session and
make it use the key.
Vino itself used to do this for example. See this:
https://git.gnome.org/browse/vino/tree/server/vino-server.desktop.in.in?h=gnome-3-12#n10

But since you have v3.14 of vino which is causing you problems,
you should also have the new vino-server.desktop file which no longer
contains the above.

I'm not sure what or why it triggering your problems and unfortunately
the backtrace didn't help me much. :(

Could you please check to make sure this file dissapears on your
system when you upgrade to vino 3.14.0-1:
/usr/share/gnome/autostart/vino-server.desktop

Maybe also "grep -R org.gnome.Vino /usr/share" and see if you can spot
something suspect.

Regards,
Andreas Henriksson

[Andreas Henriksson]

Hello!

Hi Andreas,
I can't reproduce it now either, so I am closing the bug.

I'm still very interested in knowing what caused the problem in
the first places though..... If you know of any relevant packages
you've upgrade since you where able to reproduce please tell.

Kai: If you're still able to reproduce, please if you have time
do updates only a few packages at a time and test if you can
still reproduce in between so we can narrow down what was up.

Regards,
Andreas Henriksson

PS. I just rushed another upload of vino which includes a proper
Breaks for gnome-control-center. Hopefully I managed to upload
it before the current package (which was blocked by this bug)
got a chance to migrate to testing (which doesn't yet have the
new g-c-c).

[Kai Lüke]

Ah, ok, found a file /etc/xdg/autostart/vino-server.desktop and removed
it. So this should be working now.
[Desktop Entry]
Name=Desktop Sharing
Comment=GNOME Desktop Sharing Server
Exec=/usr/lib/vino/vino-server --sm-disable
Icon=preferences-desktop-remote-desktop
OnlyShowIn=GNOME;Unity;
Terminal=false
Type=Application
AutostartCondition=GSettings org.gnome.Vino enabled
X-GNOME-Autostart-Phase=Applications
X-GNOME-AutoRestart=true
NoDisplay=false
X-Ubuntu-Gettext-Domain=vino

My Debian used to be an Ubuntu some time ago…

[Kai Lüke]

Ah, ok, found a file /etc/xdg/autostart/vino-server.desktop and removed
it. So this should be working now.
[Desktop Entry]
Name=Desktop Sharing
Comment=GNOME Desktop Sharing Server
Exec=/usr/lib/vino/vino-server --sm-disable
Icon=preferences-desktop-remote-desktop
OnlyShowIn=GNOME;Unity;
Terminal=false
Type=Application
AutostartCondition=GSettings org.gnome.Vino enabled
X-GNOME-Autostart-Phase=Applications
X-GNOME-AutoRestart=true
NoDisplay=false
X-Ubuntu-Gettext-Domain=vino

My Debian used to be an Ubuntu some time ago…

[Andreas Henriksson]

Hello Kai Lüke

Thanks for your followup!

Hello,
I also encountered this problem while running 3.14 whereever possible.
gnome-session[23651]: GLib-GIO-ERROR: Settings schema 'org.gnome.Vino'
does not contain a key named 'enabled'
aborting...

[...]

So either the schema org.gnome.Vino is wrong or gnome-session looking
for that key and this is why the error message is brought up. And
because this is an error message, g_logv will just kill the whole
process, I guess by reading the docs on g_logv: " If the log level has
been set as fatal, the abort() function is called to terminate the
program."
(https://developer.gnome.org/glib/stable/glib-Message-Logging.html)

Some more details from my side might be in place here.

The org.gnome.Vino schema dropped the "enabled" key in vino v3.14.0
(some time during 3.13.x to be more exact).

There are supposed to be no users of this in gnome 3.14.0.

(gnome-control-center 3.12.x used the key and I've already added an
appropriate Breaks in vino for it in the pkg-gnome vcs so it'll be part
of next upload.)

I've searched gnome-session but it (as far as I could find) doesn't use
this key. I suspect something else is hooking into gnome-session and
make it use the key.
Vino itself used to do this for example. See this:
https://git.gnome.org/browse/vino/tree/server/vino-server.desktop.in.in?h=gnome-3-12#n10

But since you have v3.14 of vino which is causing you problems,
you should also have the new vino-server.desktop file which no longer
contains the above.

I'm not sure what or why it triggering your problems and unfortunately
the backtrace didn't help me much. :(

Could you please check to make sure this file dissapears on your
system when you upgrade to vino 3.14.0-1:
/usr/share/gnome/autostart/vino-server.desktop

Maybe also "grep -R org.gnome.Vino /usr/share" and see if you can spot
something suspect.

Regards,
Andreas Henriksson