I have pretty same issue with evolution and its EProxy, which I made to use GSettings. It didn't have this issue earlier, when half of it was using GConf and the other half GSettings (systme proxy settings were read from GSettings, while evolution was using GConf). After migration of GConf to GSettings this got to be an issue.

----------------------------------------------------------------------------

This is what I do:
   e_proxy_init():
	proxy->priv->evolution_proxy_settings = g_settings_new ("org.gnome.evolution.shell.network-config");
	proxy->priv->proxy_settings = g_settings_new ("org.gnome.system.proxy");
	proxy->priv->proxy_http_settings = g_settings_get_child (proxy->priv->proxy_settings, "http");
	proxy->priv->proxy_https_settings = g_settings_get_child (proxy->priv->proxy_settings, "https");
	proxy->priv->proxy_socks_settings = g_settings_get_child (proxy->priv->proxy_settings, "socks");

   e_proxy_dispose ():
	if (priv->evolution_proxy_settings) {
		g_signal_handlers_disconnect_by_func (priv->evolution_proxy_settings, ep_evo_proxy_changed_cb, proxy);
		g_object_unref (priv->evolution_proxy_settings);
		priv->evolution_proxy_settings = NULL;
	}

	if (priv->proxy_settings) {
		g_signal_handlers_disconnect_by_func (priv->proxy_settings, ep_sys_proxy_changed_cb, proxy);
		g_object_unref (priv->proxy_settings);
		priv->proxy_settings = NULL;
	}

----------------------------------------------------------------------------

The schema was added during the rewrite, and opening dconf-editor at that new key claims "No Schema", thus can this crash be caused by the schema not being installed in the system directory, but in my build directory only? I'm just guessing, because I didn't see this crash before this particular change.

I overlooked in the crash catch this:
> ** GLib-GIO **: Settings schema 'org.gnome.evolution.eds-shell' is
> not installed

and realized that it does crash only if I let the evolution-calendar-factory run by DBus (it's a DBus service), but if I run it beforehand, in my develop environment, then everything works as expected.

Thus this is just about the missing GSettings schema.

Right, missing schema could be the reason. Pedro, could you please verify the gsettings-desktop-schemas is installed properly and there are no warnings/assertion fails during runtime?

I see one potential issue here - the g_settings_new() constructor could either return NULL or an object that can't do any I/O. But I think a missing schema would assert and abort the process.

The other thing that crossed my mind is that you might be using a legacy GConf backend instead of dconf. Setting the "GSETTINGS_BACKEND=dconf-settings" env. var should ensure using a dconf backend.

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/174.