Thanks for the reply Olivier. I read through the emails that you
exchanged with Dorothy. Unfortunately her problem seems unrelated to
mine. For one, I also had tried using a snapshot from 2002-12-20 (that
fixed a high-color problem I was having with Solaris), which is after
the snapshot you provided on 2002-12-02 to fix Dorothy's problem. I'm
having problems even loading PNGs.
thanks,
Ben
Olivier Chapuis wrote:
On Fri, Apr 04, 2003 at 03:25:16PM -0800, Ben Sferrazza wrote:
I've always had problems using PNG icons in FVWM, despite configuring
make to support PNG on my Sun Solaris 2.7 system. Here's the error
output to FvwmConsole.
*FvwmConsole version 2.5.6
[FVWM][GetIconFromFile]: <<ERROR>> Failed to load
/lsi/home/bsferraz/bin/fvwm-icons/konsole.png
The PNG file clearly exists there, and I've correctly added that
directory to the ImagePath in my .fvwm2rc file and have no problems
loading XPM pixmaps from that same directory.
When I use fvwm-configure to check that I indeed built in PNG support, I
get the following output.
% fvwm-config --supports
gettext
gtk
perllib
png
readline
shape
shm
sm
xpm
So it appears that I've successfully added PNG support (using
libpng-1.2.5), yet I cannot view the PNG icon in FVWM. I have no
problems viewing the same PNG using GIMP, and when trying to load in
other PNGs in FVWM, I get the same error.
Are there other things I can do to nail down the cause of this problem?
Are there other users using SPARC-based Solaris that can correctly
load PNGs with FVWM?
Can you try a recent snapshot? Dorothy Robinson report a problem with
png on a solaris/sparc system (2002-11-28). The problem was fixed just
at 2.5.6 release time and I am not sure that the fix is in 2.5.6.
Would using FvwmDebug help? For whatever reason
when I try loading the FvwmDebug module in the resource file I'm not
getting anything.
I do not think that FvwmDebug can help for this png problem.
Regards, Olivier
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
