UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Contributor
Contributor
5,872 Views
Registered: ‎09-20-2013

XSCT fails with Eclipse: Cannot open display

Jump to solution

I was getting the following Xvfb error:

 

+ xsct firmware/microzed/build/sdk.tcl -f microzed.hdf
ERROR: Xvfb is not available on the system, please make sure Xvfb is available on the system

After applying AR# 67132 by setting DISPLAY I now get:

 

+ xsct firmware/microzed/build/sdk.tcl -f microzed.hdf
Starting SDK. This could take few seconds... Eclipse: Cannot open display: 
Eclipse:
An error has occurred. See the log file
/tmp/jenkins/workspace/fsbl/microzed.sdk/.metadata/.log.
Eclipse:
GTK+ Version Check

 

This happens when launching a Jenkins (2.7.2) job on a CentOS 6.5 machine. When I execute the same command on the same machine in a VNC session I encounter no such problem.

 

Please note that Jenkins executes with limited environment settings. Is there something else I need to do to bypass the display in such an environment?

 

In attempting to reproduce it with a fresh environment and just launching XSCT I run into other issues:

 

[jhancock@watson tmp]$ env -i bash --noprofile --norc
bash-4.1$ export DISPLAY=:3.0
bash-4.1$ export TERM=xterm
bash-4.1$ . /opt/Xilinx/Vivado/2016.3/settings64.sh
bash-4.1$ xsct
/opt/Xilinx/SDK/2016.3/bin/xsct: line 123: 17469 Segmentation fault "$RDI_BINROOT"/unwrapped/"$RDI_PLATFORM$RDI_OPT_EXT"/rlwrap -rc -f "$RDI_APPROOT"/scripts/xsdb/xsdb/cmdlist -H "$HOME"/.xsctcmdhistory "$RDI_BINROOT"/loader -exec rdi_xsct "${RDI_ARGS[@]}"

 

For those who might wonder: whether I set DISPLAY to :3.0 or dummy (as the AR suggests) the results are the same.

0 Kudos
1 Solution

Accepted Solutions
Contributor
Contributor
10,402 Views
Registered: ‎09-20-2013

XSCT fails with Eclipse: Cannot open display

Jump to solution

I was able to overcome my problem in Jenkins (2.7.2) as follows.

 

  1. Install Xvfb on the machine where the Jenkins job executes.
  2. Install the "Xvfb plugin" in Jenkins.
  3. In my job select "Start Xvfb before the build, and shut it down after." and select the sub-option "Let Xvfb choose display name".
  4. In Jenkins under Manage Jenkins > Global Tool Configuration > Xvfb installation select "Xvfb installation installations" and set Name to Xvfb and Directory to /usr/bin.

The output now displays the following warning:

 

+ xsct firmware/microzed/build/sdk.tcl -f microzed.hdf
Starting SDK. This could take few seconds... Xlib:  extension "RANDR" missing on display ":0".
Xlib:  extension "RANDR" missing on display ":0".
done

 but continues to execute my script.

View solution in original post

0 Kudos
2 Replies
Contributor
Contributor
5,772 Views
Registered: ‎09-20-2013

XSCT fails with Eclipse: Cannot open display

Jump to solution

For those interested or familiar with Eclipse I've attached the indicated .log file.

0 Kudos
Contributor
Contributor
10,403 Views
Registered: ‎09-20-2013

XSCT fails with Eclipse: Cannot open display

Jump to solution

I was able to overcome my problem in Jenkins (2.7.2) as follows.

 

  1. Install Xvfb on the machine where the Jenkins job executes.
  2. Install the "Xvfb plugin" in Jenkins.
  3. In my job select "Start Xvfb before the build, and shut it down after." and select the sub-option "Let Xvfb choose display name".
  4. In Jenkins under Manage Jenkins > Global Tool Configuration > Xvfb installation select "Xvfb installation installations" and set Name to Xvfb and Directory to /usr/bin.

The output now displays the following warning:

 

+ xsct firmware/microzed/build/sdk.tcl -f microzed.hdf
Starting SDK. This could take few seconds... Xlib:  extension "RANDR" missing on display ":0".
Xlib:  extension "RANDR" missing on display ":0".
done

 but continues to execute my script.

View solution in original post

0 Kudos