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

[Kai Lüke]

Hello,

I also encountered this problem while running 3.14 whereever possible.
Here is the gdb output:

gnome-session[23651]: GLib-GIO-ERROR: Settings schema 'org.gnome.Vino'
does not contain a key named 'enabled'
aborting...

Program received signal SIGTRAP, Trace/breakpoint trap.
g_logv (log_domain=0x7ffff6c3e1b8 GLib-GIO, log_level=G_LOG_LEVEL_ERROR,
format=<optimized out>,
    args=args at entry=0x7fffffffdd80) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmessages.c:1046
1046    /build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmessages.c: Datei
oder Verzeichnis nicht gefunden.
(gdb) backtrace
#0  g_logv (log_domain=0x7ffff6c3e1b8 GLib-GIO,
log_level=G_LOG_LEVEL_ERROR, format=<optimized out>,
    args=args at entry=0x7fffffffdd80) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmessages.c:1046
#1  0x00007ffff662ef6f in g_log
(log_domain=log_domain at entry=0x7ffff6c3e1b8 GLib-GIO,
    log_level=log_level at entry=G_LOG_LEVEL_ERROR,
    format=format at entry=0x7ffff6c5dc18 Settings schema %s does not
contain a key named %s)
    at /build/glib2.0-Dv_k6u/glib2.0-2.42.0/./glib/gmessages.c:1079
#2  0x00007ffff6bf7109 in g_settings_schema_get_value (schema=0x6d5770,
key=0x72a1e0 enabled)
    at /build/glib2.0-Dv_k6u/glib2.0-2.42.0/./gio/gsettingsschema.c:951
#3  0x00007ffff6bf74b1 in g_settings_schema_key_init
(key=key at entry=0x7fffffffdf00, schema=0x6d5770,
    name=name at entry=0x72a1e0 enabled) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./gio/gsettingsschema.c:1148
#4  0x00007ffff6bfaf63 in g_settings_get_value (settings=0x6d5700,
key=0x72a1e0 enabled)
    at /build/glib2.0-Dv_k6u/glib2.0-2.42.0/./gio/gsettings.c:1091
#5  0x00007ffff6bfbf2b in g_settings_get_boolean (settings=<optimized
out>, key=<optimized out>)
    at /build/glib2.0-Dv_k6u/glib2.0-2.42.0/./gio/gsettings.c:1904
#6  0x000000000040b177 in ?? ()
#7  0x00007ffff6b9c14a in g_initable_new_valist (object_type=<optimized
out>, first_property_name=0x4214f6 desktop-filename,
    var_args=0x7fffffffe050, cancellable=0x0, error=0x7fffffffe140)
    at /build/glib2.0-Dv_k6u/glib2.0-2.42.0/./gio/ginitable.c:228
#8  0x00007ffff6b9c236 in g_initable_new (object_type=<optimized out>,
cancellable=<optimized out>, error=<optimized out>,
    first_property_name=<optimized out>) at
/build/glib2.0-Dv_k6u/glib2.0-2.42.0/./gio/ginitable.c:146
#9  0x0000000000419abd in ?? ()
#10 0x000000000041b842 in ?? ()
#11 0x000000000041c174 in ?? ()
#12 0x0000000000409115 in ?? ()
#13 0x00007ffff6257b45 in __libc_start_main (main=0x408b90, argc=2,
argv=0x7fffffffe348, init=<optimized out>,
    fini=<optimized out>, rtld_fini=<optimized out>,
stack_end=0x7fffffffe338) at libc-start.c:287
#14 0x0000000000409221 in ?? ()
(gdb) quit
A debugging session is active.

        Inferior 1 [process 23651] will be killed.

Quit anyway? (y or n) y


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)

Greetings,
Kai

On Sun, 28 Sep 2014 10:59:49 +0200 Andreas Henriksson <andreas at fatal.se>
wrote:
> Hello Ondrej!
>
> Thanks for your quick followup last time.
>
> I've found a few spare minutes to look into this but I'm completely
> failing to reproduce the issue. I also fail to see how it
> happens just from looking at the source and trying to pussle
> possible scenarios together in my head.
>
> More information on how you managed to reproduce this problem
> (and a verification that you still can reproduce it?) would
> be appreciated.
>
> Getting some backtraces from the failure state (or atleast complete
> output from the logs) would be helpful.
>
> Given my lack of time I'd say it's probably likely that I'm
> completely overlooking something obvious here, but if this
> is going to get a solution I need more input from
> someone who are able to actually reproduce the problem.
>
> Regards,
> Andreas Henriksson
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20140928/799809fa/attachment.html>