On Wed, 10 Nov 1999, Andreas Beck wrote:
> TNX for the suggestions so far. Current status:
> ----- snip -----
> LibGGI - Bug report form
> ------------------------
>
> 1. General questions:
>
> 1.a) What software platform are you using ?
> [ ] Linux [ ] Solaris [ ] Irix [ ] *BSD [ ] other Unix: ________
> [ ] other (like Win, OS/2,...): _________
>
> 1.b) What version of the abovementioned System are you using ?
> What does "uname -a" say, in case you are on a Unix variant ?
>
> 1.c) What version are your main system libraries ?
> (If libraries are missing on your system please say so.)
> libc : ___________
> libdl: ___________
>
> 1.d) What hardware platform are you using ?
> [ ] x86 [ ] SPARC [ ] Alpha [ ] 68xxx [ ] other: ________
>
>
> 2. Installation problems.
>
> 2.a) Did you have any problems in installing LibGGI ?
> Please give the error messages from the "configure" / "make" / "make install"
> commands.
>
> 2.b) If you fixed any install problems, please list what you did.
>
> 2.c) What is the exact version of LibGGI you are using ?
>
> [ ] CVS checkout at Date/Time:
> [ ] Snapshot Number:
> [ ] Release Name:
>
>
> 3. Running programs
>
> 3.a) Did the LibGGI demos (especially "demo") run after installation ?
>
> 3.b) Do they still run under the circumstances under which you experience
> your problem ?
>
> 3.c) If the demos did not run, please check, if they run on a standard X
> server, if available for your setup.
>
> 3.d) If the demos do not run, please give their diagnostic message.
>
> 3.e) Run the demos or your problematic program with LibGGI debugging enabled:
> bash$ LIBGGI_DEBUG=255 ./demo 2>libggi_debugfile or
> LIBGGI_DEBUG=255 ./problemprog 2>libggi_debugfile
>
> 3.f) Especially if you suspect a permission problem or similar, please use
> strace to gain further debugging info:
> bash$ strace ./demo 2>strace_debugfile
>
> 3.g) If your program is not a native LibGGI program, but e.g. an SVGAlib
> application running via the wrapper, please make sure that
> a) the program runs on native SVGAlib
> b) the program does not need the suid bit for anything but accessing
> graphics mode for SVGAlib, if you removed it for using it with the
> wrapper.
>
> 3.h) Do the problems occur only for specific targets ? If so, which ?
>
> 4. Fbdev/KGI specific stuff
>
> 4.a) What driver are you using ?
> [ ] Stock fbdev kernel driver
> [ ] Stock vesafb kernel VESA driver
> [ ] kgicon driver from a LibGGI snapshot/CVS
> If so: What is the kgicon configuration ?
> [ ] KGI 0.0.9 driver. Which one ?
>
> 4.b) If stock fbdev kernel driver:
> Does the driver start up correctly ? I.e. do you see a penguin at bootup ?
> Do non-GGI programs like Xfb run ?
> Does stuff like cat /some_medium_sized_file >/dev/fb0 work ?
>
> 4.c) If stock vesafb kernel VESA driver:
> See 4.b, plus:
> Does the application involved require a graphics mode that is not the
> mode you booted into ? [vesafb can NOT change modes at runtime !]
>
> 4.d) If kgicon driver:
> Does the driver build correctly ?
> Does the driver load correctly ?
> Does stuff like cat /some_medium_sized_file >/dev/fb0 work ?
>
Looks good.
> ----- snip -----
>
> Maybe we could as well make a guided problem solver for the webpages from
> that ... ?
Do you know ht://dig?
With that helpful tool, we could make a powerful search-engine for
problems in addition to the guided problem solver.
ht://dig requires a webserver which allows cgi-scripts like apache.
It comes with the SuSE-Distribution as standard, but I don't know if it
comes with RedHat or any other distributions... sorry.
>
> --
> = Andreas Beck | Email : <[EMAIL PROTECTED]> =
>
Christoph Egger
E-Mail: [EMAIL PROTECTED]
