amaya crashes: Gdk-ERROR **: BadMatch

Same happens here.
BTW shouldn´t there be a newer version of this available? (it´s at version 9.51, and even Edgy only has 8.5)

Using 8.5 under Dapper

I think that this is related to xorg/aiglx. A while ago I found a fix to stop OpenGL games becoming partly transparent under compiz: eg. export XLIB_SKIP_ARGB_VISUALS=1 && XLIB_SKIP_ARGB_VISUALS=1 blobwars. I'm using the i810 driver.

This seems to work for this issue as well under compiz and metacity: export XLIB_SKIP_ARGB_VISUALS=1 && XLIB_SKIP_ARGB_VISUALS=1 amaya

Solves the problem for me. Als using Dapper and i810.

Thanks!

I believe this is the same bug as a similar long-standing Debian amaya bug. They seem to have narrowed it down to the way amaya calls glXMakeCurrent() through libgl1-mesa-glx.

I get "serial 15072 error_code 8 request_code 142 minor_code 5"

I met the error too but I finally success in executing the program.

I download the .deb version 9.53 at http://www.w3.org/Amaya/User/BinDist.html and install it. I noticed the code have to be :

% env XLIB_SKIP_ARGB_VISUALS=1 /usr/lib/Amaya-9.53/wx/bin/amaya

and not only

% /usr/lib/Amaya-9.53/wx/bin/amaya

The program behaves normally except when I close it (I get an error that has already been reported).

In feisty beta (amaya 9.53~dfsg.0-1) I get:

(amaya:7762): 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 7363 error_code 8 request_code 142 minor_code 5)

The suggestions above to do with environment options don't seem to help. Direct rendering is off on this machine.

This bug is related to xserver-xorg-video-intel and/or xserver-xorg-video-i810.

I had xserver-xorg-video-intel installed, and got approximately the error output from Steve Dodd above. Then I replaced it with xserver-xorg-video-i810, and made a small change in xorg.conf (Driver "i810" instead of Driver "intel"), and suddenly Amaya worked.

Amaya prints the following on the terminal window from where it's started:
$ amaya
01:52:38 PM: Deleted stale lock file '/localhome/helge/.amaya-helge'.

(amaya:9935): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed

OpenGL Status:
  Software Mode = Hard
  VENDOR : Tungsten Graphics, Inc
  VERSION : 1.3 Mesa 6.5.2
  RENDERER : Mesa DRI Intel(R) 865G 20061017 x86/MMX/SSE2
  GLU Version : 1.3
  Aux buffers count 0
  Acumm rgba : 0 0 0 0

Versions:
Amaya: 9.53~dfsg.0-1
xserver-xorg-video-i810: 2:1.7.4-0ubuntu1
xserver-xorg-video-intel: 2:1.9.94-1ubuntu3
Ubuntu: Feisty, with all updates up until today.

I'm on gutsy and have the same behaviour

(amaya:8145): 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 8082 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.)

And it doesn't seem to be related to intel since I have a ati gc.

Any progress on this bug? I have Gutsy full updates as of today (2008-02-04), and Amaya 9.54. The program loads until the amaya window begins to draw, then crashes.

I have a laptop with the onboard intel hardward (915). I've been sucessfully spanning dual screens (laptop & external) with the "i810" driver, and I'm reluctant to make any changes to my xorg.conf files. Here's the output:

linux:~$ export XLIB_SKIP_ARGB_VISUALS=1 && XLIB_SKIP_ARGB_VISUALS=1 amaya
06:21:33 PM: Deleted stale lock file '/home/damon/.amaya-damon'.

(amaya:3470): 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 6981 error_code 8 request_code 158 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.)

Same problem here, I'm on Hardy Heron, I've got a toshiba a200 th1 laptop, which comes with the Intel GMA X3100 965 chipset...

http://www.toshiba.ca/web/product.grp?lg=en&section=1&group=1&product=7031&part=6476

(amaya_bin:29664): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed
The program 'amaya_bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 6601 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.)
[{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 29664
--- SIGCHLD (Child exited) @ 0 (0) ---
read(10, "", 8192) = 0
exit_group(1) = ?
Process 29663 detached

I downloaded and installed Ubuntu and amaya both within the last few days along with a whole lot of other software... so has anybody resolved this or where do I look at my logs to figure out what I did wrong? I guess this all began when i tried to get dual monitors working.

In my research I've been trying to troubleshoot opengl and flash problems, but nothing's done the trick.

Running Hardy Heron on an Asus Pundit-R

ron@ron-ws:~$ amaya
/usr/share/themes/Blubuntu/gtk-2.0/gtkrc:169: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
10:17:11: Deleted stale lock file '/home/ron/.amaya_bin-ron'.

(amaya_bin:16582): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed
The program 'amaya_bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 7011 error_code 8 request_code 158 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.)
ron@ron-ws:~$

ron@ron-ws:~$ lspci
00:00.0 Host bridge: ATI Technologies Inc Radeon 9100 IGP Host Bridge (rev 02)
00:01.0 PCI bridge: ATI Technologies Inc Radeon 9100 IGP AGP Bridge
00:13.0 USB Controller: ATI Technologies Inc OHCI USB Controller #1 (rev 01)
00:13.1 USB Controller: ATI Technologies Inc OHCI USB Controller #2 (rev 01)
00:13.2 USB Controller: ATI Technologies Inc EHCI USB Controller (rev 01)
00:14.0 SMBus: ATI Technologies Inc SMBus (rev 1a)
00:14.1 IDE interface: ATI Technologies Inc Dual Channel Bus Master PCI IDE Controller
00:14.3 ISA bridge: ATI Technologies Inc Unknown device 434c
00:14.4 PCI bridge: ATI Technologies Inc IXP200 3COM 3C920B Ethernet Controller
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller (rev 01)
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP
02:08.0 Ethernet controller: 3Com Corporation 3Com 3C920B-EMB-WNM Integrated Fast Ethernet Controller (rev 40)
02:0a.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
02:0c.0 CardBus bridge: ENE Technology Inc CB-710/2/4 Cardbus Controller (rev 02)
02:0c.1 FLASH memory: ENE Technology Inc CB710 Memory Card Reader Controller

Same problem over here.. I'm on Hardy, my PC is a AMD Athlon 2.1GHz and1Gb memory,

prodinho@ubuntu-desktop:~$ amaya
15:02:49: Deleted stale lock file '/home/prodinho/.amaya_bin-prodinho'.

[code](amaya_bin:13104): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed
The program 'amaya_bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 7089 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.)
prodinho@ubuntu-desktop:~$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0a.0 Communication controller: Conexant HSF 56k HSFi Modem (rev 01)
00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01)
01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (Secondary) (rev 01)
prodinho@ubuntu-desktop:~$[/code]

Same here, running Hardy with dual screen setup:
% amaya
17:00:49: Deleted stale lock file '/home/jyri/.amaya_bin-jyri'.

(amaya_bin:4969): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed
The program 'amaya_bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 7344 error_code 8 request_code 141 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.)

% lspci
...
02:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
02:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]

I have upgraded to Intrepid on a new Asus P5Q-EM motherboard with Intel G45 hardware.

This problem still exists for me in both the version 9.xx in the repos and in version 10 that I compiled on my own. Now, however, the assertion doesn't cause a crash:

~$ amaya
(amaya_bin:13047): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed
~$

But the rendering is very messed up under compiz. Metacity fixes the rendering problems. Under both Metacity and compiz, Amaya locks up X when I try to edit source. I'm going to file a separate bug for the rendering and locking.

I have got VMware but tried to apt-get install xserver-xorg-video-i810 . It says it is recent also tried export. But Amaya still having problem.

I have the same behavior as the previous several posts, with up-todate 8.04 as of 12/3/2008, intel 855 integrated graphics. Starting amaya (Ver 9.55 from hardy repository) from command line, it opens a window then exits immediately with:

(amaya_bin:26721): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed
The program 'amaya_bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 5727 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.)

When opened from gnome menu, program starts and runs, but attempting to navigate within display area causes contents of window to disappear.

I uninstalled the ubuntu repository version and installed the latest version 10.0 .deb from the Amaya website (as of Dec 3. 2008) Everything works OK with that package!

Same problem here on a laptop using ati video card under ubuntu intrepid
solved using the package available here :
http://www.w3.org/Amaya/User/BinDist.html

Thanks for the report. Amaya has been removed from debian and ubuntu in
Intrepid. I'm closing this report as "Won't Fix"

 status "Won't Fix"
 subscribe
 tag close-removed-intrepid