Comment on attachment 681454
workaround for old gconf
>+ /* This check is to avoid bug #541130 when old version of gnomevfs (2.16 tested)
>+ is installed then error window pops up if scheme is containing '+' character.
>+ Let's pretend these kind of schemes are not supported by gnomevfs. */
Are you sure gnomevfs is involved in gconf_client_get_* calls?
Can you point me at the GConf code that uses GnomeVFS, please?
Comment on attachment 681454
workaround for old gconf
>+ /* This check is to avoid bug #541130 when old version of gnomevfs (2.16 tested)
>+ is installed then error window pops up if scheme is containing '+' character.
>+ Let's pretend these kind of schemes are not supported by gnomevfs. */
Are you sure gnomevfs is involved in gconf_client_get_* calls?
Can you point me at the GConf code that uses GnomeVFS, please?
> GError *err = nullptr; get_string( mClient, key.get(), &err); key.Length( ) - 7, 7, NS_LITERAL_ CSTRING( "enabled" ));
> gchar *command = gconf_client_
> if (!err && command) {
> key.Replace(
Can you explain, please, why a dialog would be shown when there is a GError parameter passed to the gconf_client_get_* functions?
(Removing review request for now until we understand what is happening.)