> I still do not understand what you mean under `a nonworking svgalib'.
> The svgalib I have on my computer works. :) I've got few programs that
> make use of it (directly) and they work just fine.
Yeah. I was just mentioning, what the usual reason is. Your SVGAlib is
probably working fine.
> > also work. If it does not, it indicates a major problem with the GGI
> > installation.
> OK. The x taget works just fine. I tried to program peggy, and it showed a nice
> X-window with a picture in it.
Hmm - good and not good ...
> But it did not change the situation with peggy program.
Yeah - this problem looks very strange ...
> $ strace -o log ./peggy path/to/picture
> I checked the first log file and here is my question: what is kgi? Do I have
> to install it?
The log file is very strange. I just tried to reproduce the situation.
The failure to load genkgi.so should be nonfatal. I have myself renamed it,
and it continued working with just a warning.
However this might have been not the case in earlier revisions.
Maybe we should just rebuild the debian packages from a current snapshot ...
Where is our .deb maintainer ?
> The second one -- by:
> $ GGI_DEBUG=255 ./strace -o log2 ./peggy path/to/picture
> $ echo $?
This is even more strange. It segfaults right after loading the config
files. It should at least get to displaying the debug level.
We probably really need to rebuild the .debs ...
Sorry that I am not more helpful ...
CU, Andy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
