I'm using Gimp 2.8, on Slacko Puppy, and Gimp's Open Location feature (basically, wget built into gimp,) doesn't work. I'm running Slacko at the moment, but this error is also in Precise and Lucid.
Every time, I was using the perfectly normal SFS package (I think on Precise I used the PPM to get a .pet, but I still got the "official" ones on all 3 releases.) What's going wrong?
(That's just an example. I've tried images from other sites; I just grabbed this one because it was the first image on hand.)
[url=http://www.murga-linux.com/puppy/viewtopic.php?t=84349][img]http://i.imgur.com/Zw6vryI.png[/img][color=#3B6EA3][b][size=200] Version 27. Dotpet. Click here.[/size]
(SFS available too!)[/b][/color][/url]
so... what do I need to do? Is there a patch available? (I can NEVER manage to get code compiled, so compiling it myself is out...)
Maybe one of our experts can whip up a fix...
[url=http://www.murga-linux.com/puppy/viewtopic.php?t=84349][img]http://i.imgur.com/Zw6vryI.png[/img][color=#3B6EA3][b][size=200] Version 27. Dotpet. Click here.[/size]
(SFS available too!)[/b][/color][/url]
--without-gvfs: the choice of the backend to handle URI information, e.g., when dragging images from a browser into the Gimp, is made at compile time. This parameter will ensure that cURL is used at run-time, instead of Gvfs. You can omit this if you are installing Gvfs AND will be running gvfsd, e.g., in a GNOME desktop.
A bit above me I am afraid
Followed Semme's link after this and see it says much the same
So what is the fix?
Last edited by tytower on Sat 23 Feb 2013, 22:50, edited 1 time in total.
Hmm Ive got it compiling atm . Its a complex program. I did not have the Python headers so reinstalled python but then it wanted PyGTK 2.10.4 which I could not find so I took the compile without Python option and away it goes now so Ill see what it gets to.
I don't think it will run properly as I still don't have GVFS
I'm just tinkering atm Its a top program I use all the time
The program is 20M download semme and I am using an 80 Gig hard drive first . If it comes through I'll see what the installed size is then
Last edited by tytower on Sat 23 Feb 2013, 23:27, edited 2 times in total.
So what you think I should use curl as a backend? You only get one I think if you use --without-gvfs
: the choice of the backend to handle URI information, This parameter will ensure that cURL is used at run-time, instead of Gvfs. You can omit this if you are installing Gvfs AND will be running gvfsd, e.g., in a GNOME desktop.
Its been going for 15 minutes ,, still belting it out. Got through OK but Ill see what it does now
Last edited by tytower on Sat 23 Feb 2013, 23:39, edited 1 time in total.
Like you said, this is NOT a slap together program. It would no doubt be beneficial to view and understand the compile time options outlined for other distros. With Pups small size, I'm guessing these options become more critical cause we're dealing with far fewer libs than the larger guys include. Offhand, I don't know if there's a way to dump a given builds compile line..
I'm guessing too, the more you can omit, the smaller the final size.
This is where understanding the options come in- functionality.
Yeh OK it compiled and installed ok and works fine but there is no change on opening a picture at a URL -same message . I did expect that but just wanted to check . So I would say it needs gvfs-backends and the gvfsd running to be able to use that feature so if someone can make a version like that that would be great.
I am impressed that the version of Gimp 2.8 included with Puppy 5.4.3 as a .sfs file is right up to date . Thanks go to whoever did that.
I did not know Gimp could be opened and then web pictures dragged on to it -edited and or saved , so I would like to be able to do that.Thanks James for highlighting that.
Semme wrote:Got libcurl? Should be in the 5.4.3 repo. Follow it up with an: ldconfig << libc-bin supplies this..
3 libcurl;s come with 5.4.3 in PPM
more to install if wanted
So what does your post mean Semme?
What does ldconfig in a console do? -I tried it and it did something for a second but I am not sure what. no verbose
It essentially creates, udpates and removes symbolic links for the current shared libraries, based on the lib directories present in ld.so.conf. In other words, it'll update and make available the absolute latest shared libs introduced into the system, something the different Linux flavors don't always do. If in doubt, run it for good measure.