[wx-dev] #9547: UAI Resize Generates a X Server Problem with useBestVisual=True in GNU/Linux

[wxTrac]

Ticket URL: <http://trac.wxwidgets.org/ticket/9547>

#9547: UAI Resize Generates a X Server Problem with useBestVisual=True in
GNU/Linux
-----------------------------------+----------------------------------------
 Reporter:  john.guerra at gmail.com  |       Owner:       
     Type:  defect                 |      Status:  new  
 Priority:  normal                 |   Milestone:  2.8.8
Component:  wxPython               |     Version:       
 Keywords:  UAI, X Server Error    |   Blockedby:       
    Patch:  0                      |    Blocking:       
-----------------------------------+----------------------------------------
 Hello I trace my problem, so I will answer myself so everybody can get
 aware of this problem too.

 I looks that if you use the parameter useBestVisual=True in your wx.App,
 in GNU/Linux, then you can't use the UAI, a bug?, maybe.

 I'm attaching an example code that shows the bug, it creates two windows,
 the first one has a button that shows the second, the buggy one. In the
 second if you try to resize the UAI it breaks the app.

 The orignial post to wxpython-users
 Greetings, I have a serious problem with an application that I'm
 developing with wxPython. The Idea is to have two main Frames and have the
 ability to go from one to another using buttons and hiding and showing
 them.
 I created a main Frame and a Secondary One. At the start of the program I
 create both windows both hide the second one, and when I push a button in
 the first window I hide the first one and show the second one. Everything
 works perfectly until I started using AUIs, I replaced the sizers of the
 second window with panes in AUIs and now, when I show the second window
 and try to resize the panes in the frame draging with the mouse I got this
 error:

 The program 'python' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 44465 error_code 8 request_code 56 minor_code 0)
  (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 the program completly crashes.

 The weirdest part of the situation is that when I run the second window as
 an stand alone application everything works smothly.

 Anyone has an idea of what's happening here? Please help

 I'm using Debian Etch 4.0r3 with Python 2.4.4 , wxpython 2.8.7.1-0 from
 the deb packages, X.Org version: 7.1.1

 Thanks


--
Ticket URL: <http://trac.wxwidgets.org/ticket/9547>