Re: Segfault using apache / php4-gd / libpng
On Sat, Aug 31, 2002 at 12:11:09AM +1200, Mark Robinson wrote:
> > > Sadly however a fresh problem has emerged :
> > >
> > > [Fri Aug 30 22:39:30 2002] [notice] Apache/1.3.26 (Unix) Debian GNU/Linux configured -- resuming normal operations
> > > [Fri Aug 30 22:39:30 2002] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache/suexec)
> > > [Fri Aug 30 22:39:30 2002] [notice] Accept mutex: sysvsem (Default: sysvsem)
> > > libpng warning: Application was compiled with png.h from libpng-1.2.1
> > > libpng warning: Application is running with png.c from libpng-1.0.12
> > > gd-png: fatal libpng error: Incompatible libpng version in application and library
> > > [Fri Aug 30 22:40:21 2002] [notice] child pid 27970 exit signal Segmentation fault (11)
> > > libpng warning: Application was compiled with png.h from libpng-1.2.1
> > > libpng warning: Application is running with png.c from libpng-1.0.12
> > > gd-png: fatal libpng error: Incompatible libpng version in application and library
> > > [Fri Aug 30 22:40:22 2002] [notice] child pid 28030 exit signal Segmentation fault (11)
> > >
> > > I don't know which package to report this against, and so I toss it into the fire here.
> > I've seen this in recent evolution packages as well. In that example,
> > the package expected to use libpng2, but was actually compiled against
> > libpng3. The upshot of which is that you need to file a bug against the
> > package at fault and ask them to re-compile against libpng2.
> >
> > --Matthew
>
> True, but I don't know which package the error is happenning in.
Take a look at each of the packages you upgraded -- php4-gd2,
libgd2-xpm, and any others -- using 'apt-cache show' -- you can then see
which, if any of them, depend on libpng3.
> There are also some issues apparent with php4-gd2 which requires libgd2-noxpm and won't work with libgd2-xpm which seems to be a
> change.
Uuggghhh... don't you just hate that!
> There has been a hell of a lot of chaos in this general area recently, the libpng2/3 drama rippling down through the entire
> distribution, bad packages, severely confused package system, lots of packages being broken.
>
> Time to toss a LART somewhere for failure to plan.
>
I ended up downgrading to the evolution in sarge in order to correct my
problem... which still didn't correct the problems I was having syncing
my Palm to evolution... which made me end up ditching evolution
altogether for mutt and jpilot.
I understand that gtk+2.0 and gnome2.0 are offering some great new
features and better stability -- but they're doing so at the cost of
making applications based on the gtk+1.2 libraries incompatible. I
certainly didn't see these kind of issues when qt went to qt2 or to qt3,
for that matter.
--Matthew
Reply to: