GNOME Bugzilla – Bug 782319
Open HTTPS location
Last modified: 2018-04-22 14:01:17 UTC
Using the “File” => “Open Location...” dialogue and entering a HTTPS location (for instance https://upload.wikimedia.org/wikipedia/commons/8/84/Vanessa_indica-Silent_Valley-2016-08-14-001.jpg) results in the following error messages: Opening 'https://upload.wikimedia.org/wikipedia/commons/8/84/Vanessa_indica-Silent_Valley-2016-08-14-001.jpg' failed: Could not open 'https://upload.wikimedia.org/wikipedia/commons/8/84/Vanessa_indica-Silent_Valley-2016-08-14-001.jpg' for reading: No such file or directory I think it would be nice if GIMP could open images from HTTPS locations like it does for HTTP. GIMP version: 2.8.18 (from Debian stretch/testing)
Works fine on master, using GIO, but I get the same error on 2.8 (debian unstable). I'm pretty sure this is a duplicate and we already have a bug about this.
Bug 773920 is related - whatever dependency is used in the 2.8 builds lacks (proper) TLS support, apparently. We've also seen wget versions (one possible build dependency) without SNI support, for example.
This should now be considered as fixed by making glib-networking a hard dependency. commit 9eafce47fbe1ff47a058ca51304b33bfc8d25c3a Author: Jehan <jehan@girinstud.io> Date: Wed May 10 22:25:06 2017 +0200 Bug 773920 - Could not load or add help system - TLS/SSL support not... ... available; install glib-networking Mostly taken from commit bb196607693b2a8fa95f033966506cbf3c377d81, adding hard-dependency on glib-networking. The configure are now a bit different now, so it was just easier to copy-paste and fix rather than cherry-picking.
I'm running GIMP 2.8.20 on Xubuntu 17.10, with glib-networking 2.54.0-1, and I still can't open https URIs.
(In reply to Paulo Marcel Coelho Aragão from comment #4) > I'm running GIMP 2.8.20 on Xubuntu 17.10, with glib-networking 2.54.0-1, and > I still can't open https URIs. You should ask the Xubuntu packager. glib-networking is a runtime dependency so GIMP can still run fine if it is not found but then obviously you won't be able to open HTTPS URIs. If it is installed while not working, it probably means it is not found at runtime for a reason which pertains to how the system is set up. Therefore packagers have to make sure of this. I suggest you open a bug report at Ubuntu/Xubuntu.
Thanks, Jehan. I found a bug from 2016 on launchpad: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1649428 but the packager doesn't seem to have worked on it.
I've purge the Ubuntu package (gimp and gimp-plugin-registry), and installed gimp from the flatpak: 1. Installed flatpak 0.11.3 from ppa:alexlarsson/flatpak 2. Added a remote for flathub with: flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo 3. Installed GIMP with: flatpak install flathub org.gimp.GIMP 4. Run GIMP with: flatpak run org.gimp.GIMP So now I'm running official GIMP 2.8.22, installed as recommended in https://www.gimp.org, and I still cannot open https URLs, with exactly the same error. Therefore, it seems that this issue is not resolved/fixed.
Hmmm… indeed you are right. Something is not right on GIMP 2.8. I'm wondering if I just did a shitty job back a year ago (I normally always test my fixes, but maybe I slacked off on this one…) or if something changed. I reopen, but I have to tell you that the chances of seeing this fixed in GIMP 2.8.x are very slim. Basically we are just so close to releasing GIMP 2.10 (there is no problem for HTTPS links on 2.10) that it takes all our development time. At least for myself, I know that I won't look at this bug, sorry. ;-( Yet of course I will definitely accept and review any patches. :-)
Hey, Jehan, thanks for your patient and honest (and speed-lightning !) reply. From what you tell me, it doesn't really make sense to flog an almost dead horse — I didn't know that GIMP 2.10 was just around the corner —, my bad that I made you reopen this bug. Can't it be closed with something like 'FIXED IN THE NEXT RELEASE' ? And I'll jump ship to 2.10 right away.
Yeah don't worry. Let's leave it opened for now. We don't have any manager to please with meaningless statistics. There is a bug, it's a fact. So let's leave this opened. Who knows! Maybe someone will be bored and provide a patch! If it is still opened by the time 2.10 is out, then we'll simply close as OBSOLETE. :-)
Yeah actually we are slowly closing many 2.8-specific issues already, because it becomes pretty sure we won't get at them. GIMP 2.10 is just too close, just around the corner. So let's preemptively close this as OBSOLETE. Works just fine in 2.10. Thanks for the report anyway!
I've just installed 2.10.0-RC2, and indeed this issue is gone ! Thanks once again for your patience !