#1459: X Window System error
--------------------------+-------------------------------------------------
Reporter: andressilvam | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone:
Component: wxGUI | Version: unspecified
Keywords: | Platform: Linux
Cpu: x86-64 |
--------------------------+-------------------------------------------------
I am working normally in GRASS and suddenly shutdown the wxGUI but not the
terminal. I am working with Xubuntu 64 bits. I get the following mensagge
in the terminal:
The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 591174 error_code 162 request_code 149 minor_code 26)
(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.)
#1459: X Window System error
--------------------------+-------------------------------------------------
Reporter: andressilvam | Owner: grass-dev@…
Type: defect | Status: new
Priority: critical | Milestone:
Component: wxGUI | Version: 6.4.1
Keywords: | Platform: Linux
Cpu: x86-64 |
--------------------------+-------------------------------------------------
Changes (by artegion):
* version: unspecified => 6.4.1
Comment:
I've found the same error with GRASS 6.4.1 (2011) and Ubuntu 11.10
from GIS Layer manager selecting "add vector(Ctrl+V)",selecting some cat
(d.vect map=somemap@PERMANENT type=point,line cats=1)
press OK
(then re-open this layer (double click on it) , press again OK )* (two or
three times)
The program 'python' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 73623 error_code 174 request_code 152 minor_code 7)
(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.)
if I restart wxPython gui from terminal (g.gui) error message changes:
(.:3114): Pango-CRITICAL **: pango_layout_get_cursor_pos: assertion `index
>= 0 && index <= layout->length' failed
The program '.' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 176891 error_code 9 request_code 152 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.)
but sometimes error is:
GRASS 6.4.1 (wgs84_UTM32):~ > g.gui
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not
been called
[xcb] Aborting, sorry about that.
wxgui: ../../src/xcb_io.c:178: dequeue_pending_request: asserzione
"!xcb_xlib_unknown_req_in_deq" non riuscita.
This was not reported again for some time and it seems that it is a local
issue and no something which GRASS can fix or handle except for different
error messages and exiting. Moreover, GRASS 6.4.1 (2011) and Ubuntu 11.10
are no longer concern (not sure about that 64bit Xubuntu). So, closing
this issue as worksforme.