W3C home > Mailing lists > Public > www-amaya@w3.org > October to December 2006

[Fwd: Re: Amaya on GNU/Linux problems]

From: Leon Stringer <leon.stringer@ntlworld.com>
Date: Tue, 10 Oct 2006 22:22:42 +0100
Message-ID: <452C0F22.4020707@ntlworld.com>
To: www-amaya@w3.org

Hi,

These tests show the results for Amaya on Fedora Core 6 test versions. 
Tests 1 to 3 are built from source using the source tarball 
(amaya-fullsrc-9.52.tgz) with the Amaya directory replaced by that from 
CVS checked out today (2006-10-10).

In tests 1 to 3 the Amaya window is briefly shown before the crash. In 
test 4 it is not.

Unfortunately, I haven't received any feedback regarding this so 
although I assume that this is the current state for all FC6 systems I 
can't be certain it isn't a system-specific problem.

Please let me know if you require any other information about the 
environment (library versions etc.) or want me to try any other tests.

Regards,

Leon...
---

Environment:
	Toshiba Tecra M1 laptop
	Fedora Core 6 test 3 (with updates).
X11 device options:
	Driver	"Trident"
	BoardName   "Trident Microsystems CyberBlade XP4m32"
	Option      "AccelMethod" "EXA"

TEST 1 (--with-wx --without-dav)
$ cd Amaya
$ mkdir WX
$ cd WX
$ ../configure --with-wx --without-dav
$ cd wxWidgets_RELEASE/
$ make
$ cd ..
$ make all
$ bin/amaya
(amaya:28456): 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 8174 error_code 8 request_code 143 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.)

(The value for "serial" may change, I've seen 8175 and 8217, 8396)


TEST 2 (--with-wx --with-gl --without-dav)
$ cd Amaya
$ mkdir WX
$ cd WX
$ ../configure --with-wx --with-gl --without-dav
$ cd wxWidgets_RELEASE/
$ make
$ cd ..
$ make all
$ bin/amaya
(amaya:4071): 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 7709 error_code 8 request_code 143 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.)

(Serial may vary again)


TEST 3 (--with-wx --with-mesa --without-dav)
$ cd Amaya
$ mkdir WX
$ cd WX
$ ../configure --with-wx --with-mesa --without-dav
$ cd wxWidgets_RELEASE/
$ make
$ cd ..
$ make all
$ bin/amaya
(amaya:30438): 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 7723 error_code 8 request_code 143 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.)


TEST 4 (RPM)
Install 9.52 from W3C RPM and run "amaya":
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 348 error_code 8 request_code 145 minor_code 3)
   (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.)
Received on Tuesday, 10 October 2006 21:23:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:37 UTC