Arch Linux

hunter_thom

Member

Registered: 2011-05-02

Posts: 16

[SOLVED] GTK Bad Window

Hello,

Sorry for the newb questions, but havent been able to find any solid direction in my own searches. Any help on this would be greatly appreciated!

So I have 3 games (Kubrick, snes9x-gtk, and ePSXe) which throw nearly the same error when I start each. I do have other games that run fine. For example, VisualBoyAdvance, UT2004, and all the rest of the KDE4 games.

If it helps I run e17, arch on 32 bit.

Here are the errors when I start the games:

ePSXe:

[jesse@archbox ~]$ epsxe 
Linking executables...
`epsxe-160' -> `/opt/epsxe/epsxe'
`epsxe-152' -> `/opt/epsxe/epsxe-1.5.2'
Linking keycode file...
`keycodes.lst' -> `/opt/epsxe/keycodes.lst'
Linking BIOS files...
`bios/*.[Bb][Ii][Nn]' -> `/opt/epsxe/bios/*.[Bb][Ii][Nn]'
`bios/*.[Bb][Ii][Nn]' -> `/usr/lib/games/psemu/*.[Bb][Ii][Nn]'
`bios/*.[Bb][Ii][Nn]' -> `/usr/lib/psemu/*.[Bb][Ii][Nn]'
Linking plugins...
`plugins/libgpuPeopsMesaGL.so.1.0.78' -> `/opt/epsxe/plugins/libgpuPeopsMesaGL.so.1.0.78'
`plugins/libpadJoy-0.8.so' -> `/opt/epsxe/plugins/libpadJoy-0.8.so'
`plugins/libspuPeopsOSS.so.1.0.9' -> `/opt/epsxe/plugins/libspuPeopsOSS.so.1.0.9'
`plugins/lib*.so*' -> `/usr/lib/games/psemu/lib*.so*'
`plugins/lib*.so*' -> `/usr/lib/psemu/lib*.so*'
Linking configuration utilities...
`cfg/cfgPadJoy' -> `/opt/epsxe/cfg/cfgPadJoy'
`cfg/cfgPeopsMesaGL' -> `/opt/epsxe/cfg/cfgPeopsMesaGL'
`cfg/cfgPeopsOSS' -> `/opt/epsxe/cfg/cfgPeopsOSS'
`cfg/cfg*' -> `/usr/lib/games/psemu/cfg*'
`cfg/cfg*' -> `/usr/lib/psemu/cfg*'
Cleaning up...
removed `bios/*.[Bb][Ii][Nn]'
removed `cfg/cfg*'
removed `plugins/lib*.so*'
 * Running ePSXe emulator version 1.6.0. 
 * Memory handlers init. 
 * ePSXe: PSX BIOS loaded [/home/jesse/.epsxe/bios/PSX - SCPH1001.BIN]. 
 * Init gpu[0][libgpuPeopsMesaGL.so.1.0.78] 
Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 44 error_code 3 request_code 138 minor_code 4

snes9x-gtk:

[jesse@archbox ~]$ snes9x-gtk 

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_hue with value `adjustment16'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_saturation with value `adjustment15'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_contrast with value `adjustment14'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_brightness with value `adjustment13'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_sharpness with value `adjustment12'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_artifacts with value `adjustment11'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_gamma with value `adjustment10'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_fringing with value `adjustment9'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_bleed with value `adjustment8'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of ntsc_resolution with value `adjustment7'

(snes9x-gtk:20471): Gtk-WARNING **: Failed to get constuct only property adjustment of sound_input_rate with value `adjustment5'
The program 'snes9x-gtk' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 233 error_code 3 request_code 138 minor_code 4)
  (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.)

Kubrick:

[jesse@archbox ~]$ kubrick 
X Error: BadWindow (invalid Window parameter) 3
  Extension:    138 (Uknown extension)
  Minor opcode: 4 (Unknown request)
  Resource id:  0x220001e
QGLTempContext: Unable to create GL context.
GL Version (null)
X Error: BadWindow (invalid Window parameter) 3
  Extension:    138 (Uknown extension)
  Minor opcode: 4 (Unknown request)
  Resource id:  0x2200021
QGLContext::makeCurrent(): Failed.
QGLContext::makeCurrent(): Failed.
X Error: BadWindow (invalid Window parameter) 3
  Extension:    138 (Uknown extension)
  Minor opcode: 4 (Unknown request)
  Resource id:  0x2200075
QGLTempContext: Unable to create GL context.
QGLContext::makeCurrent(): Failed.
QGLContext::makeCurrent(): Failed.
KCrash: Application 'kubrick' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/jesse/.kde4/socket-archbox/kdeinit4__0

Any pointers or thoughts would be greatly appreciated! If any other info would be helpful let me know. Thanks!!

Last edited by hunter_thom (2011-08-01 15:22:54)

dobedo

Member

From: Belgium

Registered: 2008-10-04

Posts: 113

Re: [SOLVED] GTK Bad Window

Problem of video card driver maybe ?
What card/driver do you use ?

hunter_thom

Member

Registered: 2011-05-02

Posts: 16

Re: [SOLVED] GTK Bad Window

NVIDIA GeForce Go 7150 M is the video card itself. I'm using the proprietary nvidia driver but don't have it in front of me so not sure exact version. I'll post that when I get home.

Thanks!

hunter_thom

Member

Registered: 2011-05-02

Posts: 16

Re: [SOLVED] GTK Bad Window

Nvidia driver version: 270.41.06

GeForce 7150M / nForce 630M

Thanks. Also assaultcube does the same thing. If it helps at all here is the output:

assault cube:

[jesse@archbox ~]$ assaultcube
Using home directory: /home/jesse/.assaultcube
current locale: en_US.UTF-8
init: sdl
init: net
init: world
init: video: sdl
init: video: mode
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  138 (NV-GLX)
  Minor opcode of failed request:  4 ()
  Resource id in failed request:  0x1c0000f
  Serial number of failed request:  33
  Current serial number in output stream:  33

Seems to me like an issue with my openGL setting, no?

Here is my version of libgl:

[jesse@archbox ~]$ pacman -Si libgl
Repository     : extra
Name           : libgl
Version        : 7.10.3-1
URL            : http://mesa3d.sourceforge.net
Licenses       : custom
Groups         : None
Provides       : None
Depends On     : libdrm>=2.4.25  libxxf86vm>=1.1.1  libxdamage>=1.1.3  expat>=2.0.1
Optional Deps  : None
Conflicts With : None
Replaces       : None
Download Size  : 969.23 K
Installed Size : 3759.00 K
Packager       : Andreas Radke <andyrtr@archlinux.org>
Architecture   : i686
Build Date     : Thu 16 Jun 2011 08:19:07 AM PDT
MD5 Sum        : 95ff839ae29046b41538ad3843016898
Description    : Mesa 3-D graphics library and DRI software rasterizer

And finally, my uname:

[jesse@archbox ~]$ uname -a
Linux archbox 2.6.38-ARCH #1 SMP PREEMPT Tue Jun 7 06:40:04 UTC 2011 i686 AMD Turion(tm) 64 X2 Mobile Technology TL-60 AuthenticAMD GNU/Linux

Thanks in advance!

dobedo

Member

From: Belgium

Registered: 2008-10-04

Posts: 113

Re: [SOLVED] GTK Bad Window

Any error reported in /var/log/Xorg.0.log ?
Do you mention something specific in xorg.conf (if you have one) ?

hunter_thom

Member

Registered: 2011-05-02

Posts: 16

Re: [SOLVED] GTK Bad Window

Nothing special in xorg.conf. I just took used default, so no modifications.

I saw nothing in /var/log/Xorg.0.log, just startup details. I'll post some output a little later but nothing out of the ordinary.

Thanks

hunter_thom

Member

Registered: 2011-05-02

Posts: 16

Re: [SOLVED] GTK Bad Window

Sorry to bump, but anything else come to mind? I don't know what kind of information would help but I can post whatever helps. I appreciate any help on this.Thanks!

Meyithi

Member

From: Wirral, UK

Registered: 2009-06-21

Posts: 550

Website

Re: [SOLVED] GTK Bad Window

Something strange here, you shouldn't have libgl installed if you use nvidia drivers as nvidia provides it's own libgl.  Also, nvidia drivers are currently @ 275.21 in repos, but you are using 270.41.

Doesn't compute.

EDIT/

You may not have libgl installed after all, sorry my bad, try

[jesse@archbox ~]$ pacman -Qi libgl

instead of

[jesse@archbox ~]$ pacman -Si libgl

Last edited by Meyithi (2011-07-29 15:59:51)

---

The mind roams more freely in empty rooms.
dwm - colours - ncmpcpp - system
irc://irc.freenode.net:meyithi

hunter_thom

Member

Registered: 2011-05-02

Posts: 16

Re: [SOLVED] GTK Bad Window

Thanks Meyithi, I didnt know nvidia provded it's own libgl so I'll remove libgl and see how it goes. Also I am not using the one from the repo, I am using the one from nVidia. I had some problems before with the one from the repo (don't remember what they were) so I started using the proprietary one from nVidia.

I'll uninstall libgl, see how it goes, then maybe try using the nvidia driver from the repo, and see how that goes. Thanks for the pointers!

dobedo

Member

From: Belgium

Registered: 2008-10-04

Posts: 113

Re: [SOLVED] GTK Bad Window

I am not using the one from the repo, I am using the one from nVidia

do I miss something or the one from the repo is the nvidia one ? What about trying again the one from the repo ?

hunter_thom

Member

Registered: 2011-05-02

Posts: 16

Re: [SOLVED] GTK Bad Window

Thanks! Removing libgl, uninstalling the nVidia driver I used and installing from the repo fixed it! All works great now, thanks!

You may not have libgl installed after all, sorry my bad, try

[jesse@archbox ~]$ pacman -Qi libgl

instead of

[jesse@archbox ~]$ pacman -Si libgl

Oh my bad. Actually I did have libgl installed, just mistakenly used pacman wrong here.

do I miss something or the one from the repo is the nvidia one ? What about trying again the one from the repo ?

Sorry I mis-worded that. I meant that I had downloaded the installer from the nVidia site. At the moment I forget why, but I did originally use the driver from the repo but it caused me some problem (most likely I had mis-configured or made some mistake).