Opening files directly via http/https links in Inkscape uses gnome-vfs (a deprecated library). The dependency on gnome-vfs 1) is a build-time configure option, and 2) has runtime requirements (daemon) if used via GUI (IIRC)
Inkscape 0.92 for 16.04 is provided via inkscape-devs PPA (the distro still has 0.91): https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable
From the build log of 0.92 for 16.04: > WITH_GNOME_VFS: OFF https://launchpadlibrarian.net/302219305/buildlog_ubuntu-xenial-amd64.inkscape_0.92.0+66~ubuntu16.04.1_BUILDING.txt.gz
The Inkscape 0.92 package for Ubuntu 16.04 as offered via PPA was configured and compiled without gnome-vfs support, thus this feature is not enabled.
Progress to migrate from gnome-vfs to GIO is tracked in * Bug #715215 “Port from GnomeVFS to GIO” https://bugs.launchpad.net/inkscape/+bug/715215 (so far, no activity on this, will likely happen at some point for >= 0.93 (GTK3))
Opening files directly via http/https links in Inkscape uses gnome-vfs (a deprecated library). The dependency on gnome-vfs
1) is a build-time configure option, and
2) has runtime requirements (daemon) if used via GUI (IIRC)
Inkscape 0.92 for 16.04 is provided via inkscape-devs PPA (the distro still has 0.91): /launchpad. net/~inkscape. dev/+archive/ ubuntu/ stable
https:/
From the build log of 0.92 for 16.04: /launchpadlibra rian.net/ 302219305/ buildlog_ ubuntu- xenial- amd64.inkscape_ 0.92.0+ 66~ubuntu16. 04.1_BUILDING. txt.gz
> WITH_GNOME_VFS: OFF
https:/
The Inkscape 0.92 package for Ubuntu 16.04 as offered via PPA was configured and compiled without gnome-vfs support, thus this feature is not enabled.
Progress to migrate from gnome-vfs to GIO is tracked in /bugs.launchpad .net/inkscape/ +bug/715215
* Bug #715215 “Port from GnomeVFS to GIO”
https:/
(so far, no activity on this, will likely happen at some point for >= 0.93 (GTK3))