#21 X Error: when starting tystudio
I have installed tystudio-0.5.0-i386.sh under linux
redhat9 (shrike) very easily using default value.
runing tydemux works fine, but tyeditor open a windows
with only small squares instead of letters and I get
lot of the following:
X Error: RenderBadPicture (invalid Picture parameter) 181
Major opcode: 154
Minor opcode: 6
Resource id: 0x21005d
X Error: RenderBadPicture (invalid Picture parameter) 181
Major opcode: 154
Minor opcode: 6
Resource id: 0x21005d
X Error: RenderBadPicture (invalid Picture parameter) 181
Major opcode: 154
Minor opcode: 6
Resource id: 0x21005d
X Error: RenderBadPicture (invalid Picture parameter) 181
Major opcode: 154
Minor opcode: 6
Resource id: 0x21005d
X Error: RenderBadPicture (invalid Picture parameter) 181
Major opcode: 154
Minor opcode: 5
Resource id: 0x21005d
Following a search on the web I found that the above
are X Free86 error messages
see content of: $XFree86: xc/lib/X11/XErrorDB,v 3.40
2002/12/21 17:51:42 dawes Exp $
.
.
.
these are used in XGetErrorMessage.
XlibMessage.XError: X Error of failed request
XlibMessage.MajorCode: Major opcode of failed request: %d
XlibMessage.MinorCode: Minor opcode of failed request: %d
XlibMessage.ResourceID: Resource id in failed request:
0x%lx
XlibMessage.Value: Value in failed request: 0x%lx
XlibMessage.AtomID: Atom id in failed request: 0x%lx
XlibMessage.ErrorSerial: Serial number of failed
request: %lu
XlibMessage.CurrentSerial: Current serial number in
output stream: %lu
.
.
.
XProtoError.RENDER.1: RenderBadPicture (invalid Picture
parameter)
.
.
.
I also found the following (I don't know if that
message in a thread is relevant, just in case that's help.
* Subject: Re: strange X-window-errors
* From: "John Dailey" <john.dailey@xxxxxxxxxxxxxx>
* Date: Fri, 11 Apr 2003 13:36:36 -0400
* To: <crupp@xxxxxxxxxx>, <qt-interest@xxxxxxxxxxxxx>
By chance is your application multithreaded? I ran
into error messages like
this when doing GUI work not in the main thread. When
I did a major
reorganization to the code, the problem went away. If
this is your problem,
you should very carefully read the Threading section of
the QT docs. The two main mistakes I was making:
The application's main thread must be the thread that
calls app.exec(),
Don't alter anything related to oncreen widgets from
any thread but the main thread.
-- I thought I was safe using qApp->lock() and
qApp->unlock() but I was wrong in many cases.
-John
----- Original Message -----
From: "Christoph Rupp" <crupp@umc-web.de>
To: <qt-interest@trolltech.com>
Sent: Friday, April 11, 2003 11:22 AM
Subject: strange X-window-errors
links:
http://www.maxtux.co.uk/dist/conectiva/9.0/cd1/conectiva/cncimage/usr/X11R6/lib/X11/XErrorDB
http://lists.trolltech.com/qt-interest/2003-04/thread00736-0.html
copie d'ecran
Logged In: YES
user_id=842486
After login I can tell you that the request for support was
submitted by
pierre.moulin@btinternet.com
(sorry I should have login before)