Problem
When starting or closing a Citrix resource, the following Citrix Workspace app errors occur on IGEL OS devices:
The X Request 20.0 caused error: "3: BadWindow (invalid Window parameter)"
The X Request 55.0 caused error: "9: BadDrawable (invalid Pixmap or Window parameter)"
The X Request 60.0 caused error: "13: BadGC (invalid GC parameter)"
Solution
To suppress the error messages, configure the following registry settings in IGEL Setup:
-
Go to System > Registry > app > cwa > wfclient > thinwire30 > ignorexerrors.
-
Enable IgnoreXErrors.
-
Add the following parameters:
20.0/3, 55.0/9, 60.0/13
Further Information
The IgnoreXErrors parameter can be used as a workaround for specific X Window System errors, including: BadWindow (2.0/3, or 20.0/3), BadDrawable (55.0/9), BadGC (60.0/13).
This parameter suppresses recurring X11 error messages and allows the Citrix session to continue. This can improve the user experience in environments where the underlying graphical issue cannot be resolved immediately.
X Window System errors are typically reported in the following format:
X Request Major.Minor caused error: "Error_Code: Error_Name (Error_Description)"
The IgnoreXErrors parameter suppresses the specified X11 errors but does not resolve the underlying root cause. Additionally, ignored errors are no longer logged, which can make troubleshooting more difficult.
The following table lists common X Window System errors that can be suppressed with the IgnoreXErrors parameter:
|
IgnoreXErrors Parameter |
X Error Name |
Description |
Context in Citrix |
|---|---|---|---|
|
55.0/9 |
BadDrawable |
Invalid Pixmap or Window parameter in a drawing operation. |
Common in seamless application mode on Linux thin clients, often due to timing or window management issues. |
|
60.0/13 |
BadGC |
Invalid Graphics Context (GC) parameter used for drawing operations. |
Common in seamless application mode on Linux thin clients, related to graphical state management. |
|
2.0/3 or 20.0/3 |
BadWindow |
Operation attempted on a non-existent, invalid, or destroyed window. |
Can occur with window creation/destruction timing, or Wayland compatibility issues. |
|
2.0/6 |
BadAlloc |
Insufficient resources (e.g., memory, graphics buffers) for the requested operation. |
Indicates client-side resource exhaustion; often due to inadequate hardware or X server limits. |