Re: bug-reports amaya 8.51 and 9.51

Am Thursday 08 June 2006 16:53, sprach Irene Vatton:
>
> Yes, I guess we can force the libpng12-0 in the build.

Irene, when would it be available?

>
> There is probably a link with the following entry in .amaya/thotrc file
> GL_ACCELERATED=

I will try that out..
>
> > > In my remote setup (ssh into laptop and start amaya there but display
> > > on desktop), the amaya from the debian repository crashes with the
> > > following comment:
> > >
> > > (amaya:18003): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
> > > `!GTK_WIDGET_REALIZED (widget)' failed
> > > The program 'amaya' received an X Window System error.
> > > This probably reflects a bug in the program.
> > > The error was 'BadMatch (invalid parameter attributes)'.
> > >   (Details: serial 3225 error_code 8 request_code 144 minor_code 5)
> > >   (Note to programmers: normally, X errors are reported asynchronously;
> > >    that is, you will receive the error a while after causing it.
> > >    To debug your program, run it with the --sync command line
> > >    option to change this behavior. You can then get a meaningful
> > >    backtrace from your debugger if you break on the gdk_x_error()
> > > function.)
>
> This is a GTK 1 limitation and then a limitation of the Amaya GTK-version.

Irene, this GTK-error happened with the WX-Version 9.51. So are you mixing WX 
and GTK?

>
> The best would be to have GL hardware implementations fixed.

This may take some time :(

> But meanwhile Rigo, I don't know if it works, you could test if the debian
> package generated by Regis works with GL_ACCELERATED=no in the
> file .amaya/thot.rc

The version of Regis always behaves in the same way and always enables 
hardware acceleration. That means it ignores the GL_ACCELERATED=no variable.

> I know that this GL_ACCELERATED variable must be set to "no" on a large set
> of Windows platforms to prevent important troubles.

In my case, changing the variable does not have any effect. The version of 
amaya from the sid-repository is not usable here (unfortunately as the 
hardware acceleration makes it react real fast)

Rigo