Vivado 2018.2 crashing at startup on AMI 1.5.0

Question

Hi,  
  
Can anyone verify if they are able to run vivado (GUI-mode) on AMI 1.5.0? I tried this on two new instances and it is causing the same issue. I verified that I am forwarding X correctly with **xeyes**  
  
Here is the output

```
$ vivado

****** Vivado v2018.2_AR71275_op (64-bit)
  **** SW Build 2258646 on Thu Jun 14 20:02:38 MDT 2018
  **** IP Build 2256618 on Thu Jun 14 22:10:49 MDT 2018
    ** Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.

start_gui
java.lang.ExceptionInInitializerError
	at ui.utils.lnf.f.DB(SourceFile:945)
	at ui.utils.lnf.f.(SourceFile:71)
	at ui.frmwork.aL.dOY(SourceFile:1474)
	at ui.frmwork.aL.BL(SourceFile:1594)
	at ui.frmwork.aL.(SourceFile:1134)
	at ui.frmwork.aL.dQq(SourceFile:5415)
	at ui.PlanAhead.(SourceFile:357)
	at ui.PlanAhead.b(SourceFile:1037)
	at ui.PlanAhead.jswMain(SourceFile:1088)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 0
	at sun.font.CompositeStrike.getStrikeForSlot(CompositeStrike.java:75)
	at sun.font.CompositeStrike.getFontMetrics(CompositeStrike.java:93)
	at sun.font.FontDesignMetrics.initMatrixAndMetrics(FontDesignMetrics.java:359)
	at sun.font.FontDesignMetrics.(FontDesignMetrics.java:350)
	at sun.font.FontDesignMetrics.getMetrics(FontDesignMetrics.java:302)
	at sun.font.FontDesignMetrics.getMetrics(FontDesignMetrics.java:250)
	at sun.awt.SunToolkit.getFontMetrics(SunToolkit.java:649)
	at ui.utils.o.ag.(SourceFile:76)
	... 9 more
Exiting Vivado with a status code -1 at 1/9/19 6:08:47 AM UTC...
```

Answer

Hi Deep,  
  
Installing that font fixed the issue.  
  
Thanks!

Answer

Hey,  
We just tried it at our end and were able to successfully launch Vivado 2018.2(GUI) on AMI 1.5.0.  
  
Can you make sure that your color depth setting in RDP client is not higher than 24 Bit ?  
  
-Thanks

Answer

Hi xor,  
  
If you are using X11 forwarding without going through the GUI setup steps, you might hit a jdk bug with the default fonts that are installed with Centos.  
One way is to install fonts that don't cause this error, another way is to change the default fonts on the system and yet another way out should be to update openjdk.  
  
I think the easier/better way is to just install a new font that doesn't cause jdk to hit this bug.  
Should be fixed by installing dejavu serif :

```
 sudo yum install dejavu-serif-fonts
 ```

Let us know if this doesn't work for you.  
  
-Deep

Vivado 2018.2 crashing at startup on AMI 1.5.0

Conteúdo relevante