Eclipse IDE Crashes When Run through Secure Global Desktop, with Error: 'Xlib: extension "RANDR" missing on display'

(Doc ID 1533892.1)

Last updated on JANUARY 06, 2015

Applies to:

Oracle Secure Global Desktop - Version 4.2 to 4.63 [Release 4.0]
Information in this document applies to any platform.


Users may report that the Eclipse Integrated Development Environment version 3.8.1, when run within a Secure Global Desktop (SGD) application session, may cause the hosting ttaxpe process to exit unexpectedly.   In this scenario, the following error message can be seen as the application starts up:  Xlib:  extension "RANDR" missing on display "localhost:10.0"


This behavior may be seen at various points during the user's interaction with the Eclipse--a few are outlined in the reproduction examples below--each of them triggered by a common issue.   These details will also show how to identify and monitor the hosting ttaxpe.



In order to verify the examples outlined below, the Secure Global Desktop Administrator must identify the ttaxpe process for a user that is hosting the Eclipse application.  To do so, they will need access to a terminal window from the host where SGD is installed.   An example of this is outlined here, and this procedure will need to be revisited for each case, below.

  1. Open a terminal as 'root' on the SGD server.
  2. Use the 'tarantella emulatorsession list' command to identify the ttaxpe PID. 

bash-4.1# /opt/tarantella/bin/tarantella  emulatorsession list
User: .../_user/root
Application: .../_ens/o=applications/cn=Gnome Terminal (ultra40)
Application Server: .../_ens/o=appservers/cn=Tarantella server ultra40
Application Server DNS:
Application Server User: richardr
Protocol Engine ID: 12587
Resumable For: Session
Session ID:
Start Time: 2013-03-11 14:51:02.655
Status: Running

Protocol Engine ID indicates the process ID (PID) of the ttaxpe process ID (PID) of the ttaxpe process that is doing the emulation for the given session.   The above output would indicate PID 12857 on the SGD server,

The administrator may then monitor that PID directly, as below:

-bash-4.1# ps -fp 12587
     UID   PID  PPID   C    STIME TTY         TIME CMD
  ttasys 12587 12279   0   Mar 11 ?           0:07 /opt/tarantella/bin/bin/ttaxpe /opt/tarantella/var/log

Have this output as reference for checking / comparing the state of this process after Eclipse crashes.

Crash At Application Launch

The following steps outline the procured to reproduce this behavior at launch.

  1. Authenticate to Secure Global Desktop, and launch a local xterm application. 
  2. Refer to the Monitoring section, above, to identify the corresponding PID for the new application and begin monitoring.
  3. Launching the Eclipse application from an SGD-hosted xterm results in an error/warning message as below:
    $ eclipse/eclipse
    Xlib: extension "RANDR" missing on display "localhost:10.0".
  4. As the user enters a workspace, they may find that Eclipse will crash at the Welcome screen.


Crash while Hovering / Selecting a Variable Name

Alternatively, the following steps within the Eclipse IDE may trigger this behavior: 

  1. Go to 'File' -> 'New' -> 'Java Project'
  2. Enter a desired project name, Example: “test”
  3. Right mouse-click on the project under the Explorer on the left-hand side and go to 'New' -> 'Class'
  4. Enter 'test' as the class name. This will create a class template that looks like the extract shown below:




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms