Xorg crashes when I close the game screen

[GoogleCodeExporter]

Describe your system:
 - Linux distribution: Archlinux
 - Machine type: 32-bit
 - Mupen64Plus version: Mupen64Plus 1.5-development
 - Plugins used: Glide64, JttL's SDL Audio, blight's SDL input.

For visual artifacts, give:
 - game name and CRC/MD5 hash : POKEMON STADIUM 2
1561C75D11CEDF356A8DDB1A4A5F9D5D

- description of the artifact (missing polygons, flashing, wrong colors, etc)

When I close the games's window my Xorg crashes.

Describe the problem:

System: Linux 2.6.29-ARCH #1 SMP PREEMPT Sat May 9 12:47:43 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601000
Selinux: No
Accessibility: Disabled
GTK+ Theme: DarkRoom
Icon Theme: build
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0
timeout: 0 it_real_value: 0 frequency: 0

----------- .xsession-errors ---------------------
(II) Setting video mode 640x480...
packed pixels extension used
NPOT extension used
use_fbo 0
num_tmu 2
bebefore
bebefore2
before
after
tbuf_size 2Mb
R4300 core finished.
[JttL's SDL Audio plugin] Cleaning up SDL sound plugin...
[blight's SDL input plugin]: Closing...
mupen64plus: Fatal IO error 0 (Success) on X server :0.0.
43d5978b-7a3d-38b5-7c0c22e5-70f8bd13 is dumped
--------------------------------------------------

Original issue reported on code.google.com by berksons...@gmail.com on 18 May 2009 at 5:44

Attachments:

• mupen64plus-bugreport.txt

[GoogleCodeExporter]

This is not a Mupen64Plus bug; it should not be able to crash the X server.  
This is
likely due to a bug in your opengl driver.  What kind of graphics adapter do 
you have?

Original comment by richard...@gmail.com on 9 Jul 2009 at 2:06

• Changed state: Invalid

[GoogleCodeExporter]

I'm using this driver:

local/xf86-video-intel 2.7.1-1 (xorg-video-drivers)
    X.org Intel i810/i830/i915/945G/G965+ video drivers

Original comment by berksons...@gmail.com on 9 Jul 2009 at 2:27

[GoogleCodeExporter]

All I can say is keep updating and wait for Intel to fix the bug.  I have an 
HTPC
with the Intel 965 chipset and their drivers have been going through major 
changes
and refactoring.  I believe that the very latest code is somewhat stable, but 
to get
it you'd probably have to build and install it yourself.

Original comment by richard...@gmail.com on 22 Jul 2009 at 4:46