My fix works for RHEL5, where's no gio, so I can't recompile with --enable-gio there. You may consider to disable gio in your builds, because as you say Ubuntu is using early version of gio and it is probably only wrapper to gvfs (when you experience same popup error window as gvfs creates). Upstream switched to gio as default quite recently (until that time gvfs was used as default) so there shouldn't be a problem for older systems to stay with gvfs only.
I don't like the idea to filter some schemes for all users just because some legacy libraries used by LTS distributions are buggy (we should actually fix these libraries). As long as gvfs is not used by mozilla as default we could add this hack to gvfs code. I would like to keep gio code untouched.
My fix works for RHEL5, where's no gio, so I can't recompile with --enable-gio there. You may consider to disable gio in your builds, because as you say Ubuntu is using early version of gio and it is probably only wrapper to gvfs (when you experience same popup error window as gvfs creates). Upstream switched to gio as default quite recently (until that time gvfs was used as default) so there shouldn't be a problem for older systems to stay with gvfs only.
I don't like the idea to filter some schemes for all users just because some legacy libraries used by LTS distributions are buggy (we should actually fix these libraries). As long as gvfs is not used by mozilla as default we could add this hack to gvfs code. I would like to keep gio code untouched.