Opened 9 years ago

Closed 6 years ago

#1362 closed defect (fixed)

wxpython GUI closes suddenly

Reported by: lluis Owned by: grass-dev@…
Priority: normal Milestone: 7.0.0
Component: wxGUI Version: svn-trunk
Keywords: wxpython, X Windows error, Cc:
CPU: x86-64 Platform: Linux

Description

I start grass70 with the wxpython interface and when I open a menu or a window (for example, when I try to load a vector layer in de map display) the GUI closes suddenly and I can read this message in the terminal:

"GRASS 7.0.svn (girona_4326):~ > The program 'python' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength? (poly request too large or internal Xlib length erro'.

(Details: serial 17612 error_code 16 request_code 153 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.)

"

Change History (8)

comment:1 Changed 9 years ago by mlennert

I can confirm this behaviour, and it seems to be linked specifically to adding vectors to the display, although I cannot confirm this with absolute certitude. The crash does not happen systematically, and sometimes I don't get a crash, but a freeze. Using g.gisenv set=WX_DEBUG=5 I see that it seems to happen just after a v.db.connect call.

I for myself am on Debian Squeeze, with wx 2.8.10. I haven't tried the --sync debugging hinted at in the error message.

Moritz

comment:2 Changed 9 years ago by mmetz

I can confirm this behaviour on Fedora 14 with wx 2.8.11, all versions of GRASS.

Markus M

comment:3 in reply to:  2 ; Changed 9 years ago by martinl

Replying to mmetz:

I can confirm this behaviour on Fedora 14 with wx 2.8.11, all versions of GRASS.

really all version of GRASS??? I know about this bug only in G7.

comment:4 in reply to:  3 ; Changed 9 years ago by mlennert

Replying to martinl:

Replying to mmetz:

I can confirm this behaviour on Fedora 14 with wx 2.8.11, all versions of GRASS.

really all version of GRASS??? I know about this bug only in G7.

No, I've encountered it in 6.4.1 and 6.5 as well.

Moritz

comment:5 in reply to:  4 ; Changed 9 years ago by mmetz

Replying to mlennert:

Replying to martinl:

Replying to mmetz:

I can confirm this behaviour on Fedora 14 with wx 2.8.11, all versions of GRASS.

really all version of GRASS??? I know about this bug only in G7.

No, I've encountered it in 6.4.1 and 6.5 as well.

AFAICT, there were numerous bugs. The most serious bug was that vector maps can have no DB link, but this was not taken into account by v.db.connect and the wxGUI. The wxGui had other bugs, mostly related to incorrect handling of return codes and output / error messages of modules called by the wxGUI. I hope I fixed some of these bugs for trunk in r46277 and previous. Martin, please test my changes and backport what passes your testing (after some improvement if needed).

Markus M

comment:6 in reply to:  5 Changed 9 years ago by martinl

Replying to mmetz:

modules called by the wxGUI. I hope I fixed some of these bugs for trunk in r46277 and previous. > Martin, please test my changes and backport what passes your testing (after some improvement if

backported in r46295 and r46296 with little change in debug messages

comment:7 Changed 6 years ago by annakrat

I don't recall such problems recently, so I am closing this ticket, reopen if needed.

comment:8 Changed 6 years ago by annakrat

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.