Am Mittwoch, 2. Januar 2002 02:08 schrieb Trevor Johnston:
> I upgraded to libqt2_2.3.1-18 this evening, and the icon problem gone too.
> Except the splashscreen on startup and the "head pictures" in kdm, which
> now do not appear. They appeared before this upgrade, but no icons did!
Try upgradin
On Tue, Jan 01, 2002 at 11:55:34PM +, John Gay wrote:
> > libqt was still 2.3.1-18 but the icon problem had vanished. I did log out,
> > restart my X-server, and log in. Regardless, the problem is gone from my
> > system.
> Is this confirmation that the icon problem is fixed, or just one luc
On Tuesday 01 January 2002 00:26, Robert Tilley wrote:
> I recently had problems with lost icons and downgraded to libqt 2.3.1-17
> from 2.3.1-18 which seemed to solve the problem.
>
> In a recent system update, libqt was again upgraded to -18 and icon problem
> recurred. Later that night 12-31-01
Colin Watson <[EMAIL PROTECTED]> writes:
> The problem appears to be that libqt2 now links to libpng3 rather than
> libpng2. When the dynamic linker loads a QT-dependent application still
> linked against libpng2, it overrides libqt2's png symbols with the png
> symbols defined in the application,
* Colin Watson <[EMAIL PROTECTED]> [020101 15:44]:
> > > binary packages built from kdeutils depend on libpng directly. Why?
> >
> > I can only guess, but I heard that are systems where an shared library
> > can not depent on other shared libraries so the application has to
> > link against all. P
On Tue, Jan 01, 2002 at 03:41:54PM +0100, Bernhard R. Link wrote:
> * Colin Watson <[EMAIL PROTECTED]> [020101 15:08]:
> > I'm also a little confused by why so many KDE applications link to
> > libpng directly. Picking kdeutils at random, the only instances of
> > 'png_' or 'png.h' anywhere in the
* Colin Watson <[EMAIL PROTECTED]> [020101 15:08]:
> I'm also a little confused by why so many KDE applications link to
> libpng directly. Picking kdeutils at random, the only instances of
> 'png_' or 'png.h' anywhere in the source tree are in
> admin/acinclude.m4.in, yet -lpng is on the link line
On Tue, Jan 01, 2002 at 02:53:51PM +0100, Laurent Jacques wrote:
> Thank you very much. It solves my problem (cfr. "kde & docking tray problem").
> Is it possible to integrate this change into the libpng3 package, I mean,
> create the symbolic link
> ln -s /usr/lib/libpng.so.3.1.2.1 /usr/lib
On Tue, Jan 01, 2002 at 07:39:07PM +1100, Mark Purcell wrote:
> Btw, this appears to be a major backwards incompatibily problem
> between libpng2 -> 3 which effects lots and lots of packages.
> The solution is rather simple, requiring recompilation to
> get the correct linkage to libpng3, but it wo
Thank you very much. It solves my problem (cfr. "kde & docking tray problem").
Is it possible to integrate this change into the libpng3 package, I mean,
create the symbolic link
ln -s /usr/lib/libpng.so.3.1.2.1 /usr/lib/libpng.so.2
into libpng3_1.2.1-1_i386.deb ?
Is it clean enough for a d
On Tue, 1 Jan 2002 21:25:24 +1100
Mark Purcell <[EMAIL PROTECTED]> wrote:
> The incompatibility as I see it from here is that any application
> which depends on libpng2, is only good with libpng2 <= 1.0.12-2 and
> upon recompiling will be dependant on libpng3.
>
> libqt 2.3.1-18 has been recompil
On Tue, Jan 01, 2002 at 06:50:03PM +0900, Junichi Uekawa wrote:
> On Tue, 1 Jan 2002 19:39:07 +1100 Mark Purcell <[EMAIL PROTECTED]> wrote:
>
> > The solution is rather simple, requiring recompilation to
> > get the correct linkage to libpng3, but it would of been nice to
> > see some dicussion on
12 matches
Mail list logo
