I've had similar problems to the ones described below. I thought it
was something with my system, so I have not filed a bug report (to
Debian). What happens for me is that if I use the libggi from the
Debian packages on kgicon, I get a black screen. If I
"GGI_DEBUG=255 ./demo" I get a segfault. If I use it on the X target,
however, it works without problems. I've also got a recent libggi in
/usr/local, which works on kgicon.
I thought this had sometihing to do with me having outdated files in
/etc/ggi as Debians packages normally don't replace those files (and
libggi had its settings there even when it was installed in /usr/local
earlier), but copying /usr/local/etc/ggi to /etc/ggi didn't change a
thing.
Then I tried copying the GGI targets from /usr/local/lib to
/usr/lib. This didn't work either.
I thought maybe the Debian package was outdated, so I recreated it
from a recent (at the time) CVS snapshot of GGI. Didn't work.
Well, /usr/local/lib/libggi.so works, so it's not the end of the
world. It would be nice if the Debian package would work, as it's
convenient to be able to just select programs to get them downloaded
and installed, and all libggi-using programs in Debian are linked with
/usr/lib/libggi.so...
--
Niklas
On Sun, Oct 10, 1999 at 09:47:35PM +0200, Andreas Beck wrote:
> Hi !
>
> > and libgii0{,-dev} (as it seems to be necessary according to dependancies).
>
> Yes. Looks good.
>
> > vesafb: mode is 1024x768x16, linelength=2048, pages=0
> > Console: switching to colour frame buffer device 128x48
>
> O.K. - also looks good.
>
> > > SVGAlib, which only happens as "last-resort", i.e. when the framebuffer
> > > device does not work as expected.
> > I do not think it's ever possible as I have not installed
> > libggi-target-svgalib.
>
> Right. However an unresponsive terminal is usually only encountered when
> using a nonworking SVGAlib, so that was my first guess.
>
> > > That doesn't sound like fbcon at all. A nonworking SVGAlib usually causes
> > > this.
> > Do you mean a nonworking SVGAlib target for libggi?
> No, a nonworking SVGAlib. Our target works nice, but many systems have
> problems with SVGAlib. However, as you have not installed the target, LibGGI
> will never touch SVGAlib, so that possibility is ruled out.
>
> > > First check that your LibGGI distribution is intact. For this, start X and
> > > run a GGI demo under X. It should pop up in an X window. If that doesn't
> > > happen, something is wrong with the LibGGI installation.
> > Hmm... This means I should install x-target, I will try.
>
> Good. That will rule out much of the possible mode negotiation and other
> compatibility problems, as if any X application works, the x target should
> also work. If it does not, it indicates a major problem with the XGGI
> installation.
>
> > > Then check, that you are really on a fbcon system. Does e.g. cat </dev/fb
> > > >/dev/null work ?
> > It looks like I do not have this device. I do have a whole bunch of /dev/fb?*,
> > but no /dev/fb. This could be the reason.
>
> No. We actually try /dev/fb0. Try with that one, please. Sorry, I have that
> symlink ... my fault.
>
> > > At that stage, there should at least be no more lockups. If there are still
> > > problems, run the "demo" application with "bash$ GGI_DEBUG=255 ./demo".
> > This one just core dumps (I tried it before sending my plea for help :).
>
> Oh - that seems like a major problem with the LibGGI installation. It dumps
> core before giving a single line of debug info ?
> Try finding out where it dumps (strace, gdb) or install a source
> distribution of LibGGI, as this will rule out any binary incompatibilities.
>
> CU, Andy
>
> --
> = Andreas Beck | Email : <[EMAIL PROTECTED]> =
>
