reassign 332312 libgnomeui32 1.4.2-24 severity 332312 important thanks I can reproduce this bug by upgrading libgnomeui32 to version 1.4.2-24, and clear it by (forcibly) downgrading just this package to the testing version. Even with other library combinations which result in loading gdk_imlib1 and gdk_imlib11 simultaneously, only the new version of libgnomeui32 causes this problem.
Using the old version of libgnomeui32 with either the old or the new version of gdk-imlib1 (which is a wrapper around gdk-imlib11) does *not* show the problem; the problem seems to somehow be specific to how the new libgnomeui32 binary was built, and is not dependent on any internal differences between the gdk_imlib versions. Likewise, forcing the new libgnomeui32 to use the old gdk-imlib1 doesn't make any difference in the behavior. It seems that a bug like this has been seen before -- bug #190884, the last time png linkage changed... I'm not sure it's the same bug, though, since libgnomeui32 is no longer linked directly against libpng as it appears to have done at the time. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
