Xlib: unexpected async reply (sequence 0x3a0e)!

[Neithan]

I managed to boot successfuly one time, I could get the P00>>> prompt, and issue
commands: show devices, show config, and even boot from a OpenVMS iso.

P00>> b DQB0

All went well, till I got:

Xlib: unexpected async reply (sequence 0x3a0e)!

then the emulator stop doing any activity.

The next attemps to launch ./es40 again shows the same Xlib error even before I can get the prompt.
I would be glad to provide more information to debug this.

Regards,

Juan

[Brian Wheeler]

Which gui are you using:  X11 or sdl?  It could be a threading issue since it doesn't seem terribly predictable...

Brian

[Neithan]

* On my previous report I was using gui=sdl on es40.cfg.

* With gui=X11 in es40.cfg, and OPTIONS = -DHAVE_SDL -DHAVE_X11 -DHAVE_PCAP -DHAVE_NEW_IDE in Makefile I get.

--
%GUI-I-INS: Installing x11 module as the ES40 GUI
sys0(tsunami): $Id: System.cpp,v 1.62 2008/02/08 20:08:13 iamcamiel Exp $
sys0(tsunami): $Id: DPR.cpp,v 1.15 2007/12/30 15:10:22 iamcamiel Exp $
sys0(tsunami): $Id: Flash.cpp,v 1.15 2007/12/30 15:10:22 iamcamiel Exp $
cpu0(ev68cb): $Id: AlphaCPU.cpp,v 1.67 2008/02/08 20:08:13 iamcamiel Exp $
%VGA-I-ROMSIZE: ROM is 39936 bytes.
XAllocColorCells returns error. Maybe your screen does not support a private colormap?  
font 8 wide x 16 high, display depth = 24  
X Error of failed request:  BadAccess (attempt to access private resource denied)
  Major opcode of failed request:  89 (X_StoreColors)
  Serial number of failed request:  12
  Current serial number in output stream:  274

--
Thanks for your repliess

[Brian Wheeler]

In the gui section, add

private_colormap = false;

Also, you may want to comment out the "XWarpPointer" call around line 1507 in src/gui/gui_x11.cpp

so you can keep track of your mouse.

Brian

[Neithan]

Thanks Brian,

I tried it with latest cvs sources and your changes.
I still got:  "Xlib: unexpected async reply".

But...I found the cause: I was running it with sudo.

I did a chown to all the tree and set the same user that is running X. And run the emulator: ./es40 with that user. All ran smoothly.

Juan

[David Leonard]

I still get that error, regardles of which user runs the emulator.
The solution I found was to delete all the rom files that had been created by es40.