Informix Error -55352: Unable to open display ''.
Cause and resolution
Unable to open display ''.
If the DISPLAY environment variable is undefined (for instance, after executing the rlogin or su command), define it.
If the X server access control facility is activated for this DISPLAY, you might need to run the xhost
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-55352 fires when the oncockpit GUI client can't open its X11 display — per the official
guidance, two causes are named.
- The
DISPLAYenvironment variable left undefined, per the official guidance — commonly after anrloginorsuthat didn't preserve it. - The X server's access control facility blocking the connection, per the official
guidance, if
xhosthasn't granted access to the connecting host.
Solutions / Resolution
- Define the
DISPLAYenvironment variable, per the official guidance, if it's unset. - Run
xhost <hostname>from the local computer (the one named byDISPLAY), per the official guidance, if the X server's access control is active.
Examples
Checking and granting X display access
$ echo $DISPLAY
$ xhost <hostname>
Per the official guidance, xhost must be run from the local computer that DISPLAY specifies,
not from the remote host trying to connect.
Diagnostic Checks
- Check whether
DISPLAYis set in the environmentoncockpitruns in. - Check whether the X server's access control facility is active, and run
xhostfrom the correct (local) computer if so.
Related Errors / Related Topics
- -55276 — "connect() to host... using service... failed." Another
oncockpit/onprobeconnectivity error, at the network layer rather than the X11 display layer.
oncockpit couldn't open its X11 display — check that DISPLAY is set, and that xhost has
granted access from the correct local computer if X access control is active.