Re: [Gimp-user] PNG troubles

[Ofnuts <ofnuts gmx com>]

On 08/02/18 02:00, Ruben Safir wrote:
> > elicits an "internal server error".
>
> Of course.  That is what we are talking about.  It doesn't render the
> orignal  png file so the server can't created through imagemagik the
> file images that are resized.  I tried to make this understandable in the original post.
> If I failed, I'd be happy to try to explain it again.  But the server
> can not produce images from png files because they are failing to be
> rendered, and neither can the GIMP on the desktop.
>
> > http://images.mrbrklyn.com/brooklyn/ornimental_building_kent_st_2006_00557.png returns a 2K  file with HTML contents, 
> > even if it is named "ornimental_building_kent_st_2006_00557.png". So of course it isn't a valid image file 
> > for image editors
> That is not an image.  It IS an HTML file.  (your eyes are not playing
> tricks on you).  That is not the file being opened by the program.
> It is the html generated by the program that normally contains an image
> generated by the server generated from an original.
>
> > http://www.mrbrklyn.com/brooklyn/images/ornimental_building_kent_st_2006_00557.png is correct.
> >
> > So IMHO before you cast doubts on the PNG format or Gimp, better
> > check that your server is fully functional.
> The server has been fully function since 1998.
>
> Maybe you can right click on the PNG file and try to open it with the
> gimp and see if it renders on GNU/Linux.
Then, to eliminate all other hypotheses:

1. post  the initial image outside of your server (Dropbox or else..., 
**not** an image server, that could recompresss it). MD5 or SHA checksum 
also a good option.

2. describe exactly how you save it to PNG in Gimp or what you do to it 
with ImageMagick (with actual software versions used)

3. post the image you obtain on the same server as 1) so that we can 
check we obtain the same thing.

Now, about your server being fully functional since 1998... Since you 
complain about recent version of software, I assume you have been doing 
software upgrades, and not only on imaging software, and maybe even move 
the server to new hardware a couple of times.... These could have 
introduced problems as well...