Java Can't connect to X11 window server using 'localhost:10.0' as the value of the DISPLAY variable

Question

I have a script using java to connect to display X11 in the port 10.0 at localhost

but i get always this error

java.lang.InternalError: Can't connect to X11 window server using 'localhost:10.0' as the value of the DISPLAY variable.
    at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
    at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:62)
    at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:178)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:142)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:186)
    at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:82)
    at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:112)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:186)
    at java.awt.Toolkit$2.run(Toolkit.java:849)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:841)
    at ij.io.Opener.openJpegOrGif(Opener.java:367)
    at ij.io.Opener.openImage(Opener.java:220)
    at ij.io.Opener.openImage(Opener.java:249)
    at ij.io.Opener.open(Opener.java:116)
    at ij.IJ.open(IJ.java:1112)
    at ij.macro.Functions.open(Functions.java:2006)
    at ij.macro.Functions.doFunction(Functions.java:129)
    at ij.macro.Interpreter.doStatement(Interpreter.java:205)
    at ij.macro.Interpreter.doBlock(Interpreter.java:515)
    at ij.macro.Interpreter.runUserFunction(Interpreter.java:278)
    at ij.macro.Interpreter.getFactor(Interpreter.java:1200)
    at ij.macro.Interpreter.getTerm(Interpreter.java:1162)
    at ij.macro.Interpreter.getExpression(Interpreter.java:1145)
    at ij.macro.Interpreter.getBooleanExpression(Interpreter.java:881)
    at ij.macro.Interpreter.getLogicalExpression(Interpreter.java:857)
    at ij.macro.Interpreter.getBoolean(Interpreter.java:850)
    at ij.macro.Interpreter.doIf(Interpreter.java:829)
    at ij.macro.Interpreter.doStatement(Interpreter.java:217)
    at ij.macro.Interpreter.doBlock(Interpreter.java:515)
    at ij.macro.Interpreter.doStatement(Interpreter.java:241)
    at ij.macro.Interpreter.doIf(Interpreter.java:831)
    at ij.macro.Interpreter.doStatement(Interpreter.java:217)
    at ij.macro.Interpreter.doStatements(Interpreter.java:195)
    at ij.macro.Interpreter.run(Interpreter.java:99)
    at ij.macro.Interpreter.run(Interpreter.java:65)
    at ij.macro.Interpreter.run(Interpreter.java:75)
    at ij.plugin.Macro_Runner.runMacro(Macro_Runner.java:127)
    at ij.plugin.Macro_Runner.runMacroFile(Macro_Runner.java:112)
    at ij.IJ.runMacroFile(IJ.java:103)
    at ij.ImageJ.main(ImageJ.java:517)

I have tried everything to solve this problem like :

export DISPLAY=:10.0
export DISPLAY=localhost:10.0

I tried also the port 0.0 but i get always the same error

after trying xhost

xhost +local:all
xhost:  unable to open display ""
xhost:  unable to open display ":10.0"

how can i fix this i thought that the X Server is not runing so i tried startx its says its runing at that port

my system is Ubuntu server edition 10.04

If also using a VNC viewer via ssh: after modifying the `xhost` access list, it is necessary to reopen the SSH connection. At least on my current setup (VNC to Debian), I infer that it needs to get an updated xhost access list. — Technophile, Sep 02 '21 at 23:54

score 73 · Answer 1 · edited Mar 25 '14 at 10:10

73

You need to specify the -Djava.awt.headless=true parameter at startup time.

edited Mar 25 '14 at 10:10

gawi

2,843
4
29
44

answered Apr 15 '12 at 20:42

Michael-O

18,123
6
55
121

Thanks alot but where i have to specify this exactly ? – Elteroooo Apr 15 '12 at 21:31
2

Exception in thread "main" java.awt.He adlessException at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:1 73) – Elteroooo Apr 15 '12 at 21:50
Are you running a security manager? If so, you maybe have to grant permission to. – Michael-O Apr 16 '12 at 09:57
2

thanks the problem was that the X Server is running in another port – Elteroooo Apr 18 '12 at 16:06
i got the same problem on another server and its because the driver – Elteroooo Apr 18 '12 at 16:07
This solved my problem with a Jenkins build. It just suddenly STOPPED working, and adding this flag to the maven command line fixed it. Thanks! – Jim Jarrett Nov 26 '12 at 14:32
This worked for me. In Jenkins -> Build -> Goals and options -> -Djava.awt.headless=true test In my case clean compile -Djava.awt.headless=true test – user358591 Dec 18 '17 at 21:01
5

The asker's program wants to do `ij.io.Opener.openJpegOrGif`, we can guess that probably requires a GUI. So headless would result in another error: `java.awt.HeadlessException`. – Nicolas Raoul Feb 22 '18 at 08:23
with this true - i got error: java.awt.AWTException: headless environment – Pankaj Kumar Katiyar Sep 22 '18 at 03:16
This prevents the error, but now the GUI popup that is supposed to go to my main display just does not exist at all... – Eliezer Miron Mar 09 '22 at 22:32

score 52 · Answer 2 · answered Dec 10 '12 at 21:20

52

Remove the DISPLAY variable

unset DISPLAY

This helps in most cases (e.g. starting application servers or other java based tools) and avoids to modify all that many command lines.

It can also be comfortable to add it to the .bash_profile for a dedicated app-server/tools user.

answered Dec 10 '12 at 21:20

bebbo

2,830
1
32
37

3

it didn't help me at all. I got this: AWT Can't connect to X11 window server using... – Pankaj Kumar Katiyar Sep 22 '18 at 03:17
If your app uses awt then you must set DISPLAY correctly. This is for apps not using awt. – bebbo Sep 22 '18 at 07:41
1

When playing around with this, make sure you restart mobaXterm after adding the unset command in your bashfile. Since the Display variable will be set from before and just running your bash file won't change that. – mrk Dec 07 '18 at 18:38
This works when I use Putty + Xming Server:0.0. Unfortunately, I have the same error when using wsl2. I haven`t tried mobaXterm, but, you need to restart Xming after adding the unset command as well – Viki Liu Mar 24 '23 at 20:23

score 48 · Accepted Answer · answered Feb 25 '13 at 13:54

48

This command helped me to solve the problem:

export DISPLAY=:0

answered Feb 25 '13 at 13:54

Maryam Saeidi

1,463
2
21
33

47

`unset DISPLAY` helped me (with `export DISPLAY=:0` I got the error `Can't connect to X11 window server using ':0'` – beluchin Dec 11 '15 at 15:41
3

well sometime - it won't work on linux then its good to install Xvfb with apt and run it on any screen like: Xvfb :1 and then set variable in build phase -- export DISPLAY=:1 --> this perfectly works. – Pankaj Kumar Katiyar Sep 22 '18 at 03:39
Please, read: this https://stackoverflow.com/questions/20607777/what-display-settings-needed-for-running-sh-installer-for-java-7-ee-sdk-on-mac – Felix Aballi Feb 20 '19 at 17:36

score 29 · Answer 4 · answered Jul 05 '17 at 09:07

29

I think you are working in sudo mode.Please checkout to the user mode and try again

answered Jul 05 '17 at 09:07

Harsh V Pillai

299
3
2

7

This was my problem as well. Seems odd to not be able to run as root though, right? – barbiepylon Aug 19 '17 at 20:52
Why I can't use sudo ? – Andrea Borgogelli Avveduti Dec 11 '17 at 09:34
@javajavajava yup – Harsh V Pillai Jan 05 '18 at 07:59
1

Worked for me.. think the X11 server can only be started by the owner of the current session in my case root – denniz crypto Nov 20 '20 at 19:41
Seems the same problem for me. Had to start `Xvfb` from out my gitlab pipeline, could not do that in the docker image itself. – Jacob van Lingen Dec 12 '22 at 15:29

score 9 · Answer 5 · answered May 22 '14 at 13:47

In case anybody trying to run the automated unit tests via maven-surefire-plugin on CI(jenkins,..), and getting the above mentioned error, be sure to update your surefire plugin configuration :

<plugin>
     <groupId>org.apache.maven.plugins</groupId>
     <artifactId>maven-surefire-plugin</artifactId>
     <version>${maven-surefire-plugin.version}</version>
     <configuration>
            <systemPropertyVariables>
                <java.awt.headless>true</java.awt.headless>
            </systemPropertyVariables>
      </configuration>
</plugin>

how to do it in gradle and also how to set the property value in it. — Sobhit Sharma, Dec 22 '18 at 13:21

score 8 · Answer 6 · edited Nov 08 '16 at 10:58

8

This will fix it:

/usr/bin/java -Djava.awt.headless=true $Your_program

edited Nov 08 '16 at 10:58

Frederico Martins

1,081
1
12
25

answered Jul 17 '12 at 15:00

grepit

21,260
6
105
81

3

Did not fix mine – Alex Shnyrov Mar 31 '20 at 00:40
1

This worked for me. Thank you. I was getting the error because I'm using poi. – dev4life Apr 15 '20 at 18:49

score 7 · Answer 7 · answered Jul 03 '17 at 10:46

7

For me logging in as -Y instead of -X worked.

In case you've got untrusted X11 as shown below, then try -Y flag instead (if you trust the host):

Warning: untrusted X11 forwarding setup failed: xauth key data not generated

answered Jul 03 '17 at 10:46

loknath

738
2
8
20

score 6 · Answer 8 · answered Apr 14 '20 at 11:57

If you are trying to export display using su and it still doesn't work. This is what worked for me. Try X11 forwarding for sudo users.

Connect the remote host using the -X option with ssh.

# ssh -X root@remote-host

Now list the coockie set for the current user.

# xauth list $DISPLAY
    node01.thegeekdiary.com/unix:10  MIT-MAGIC-COOKIE-1  dacbc5765ec54a1d7115a172147866aa
# echo $DSIPLAY
    localhost:10.0

Switch to another user account using sudo. Add the cookie from the command output above to the sudo user.

# sudo su - [user]
# xauth add node01.thegeekdiary.com/unix:10  MIT-MAGIC-COOKIE-1  dacbc5765ec54a1d7115a172147866aa

Export the display from step 2 again for the sudo user. Try the command xclock to verify if the x client applications are working as expected.

# export DISPLAY=localhost:10.0

source: https://www.thegeekdiary.com/how-to-set-x11-forwarding-export-remote-display-for-users-who-switch-accounts-using-sudo/

score 6 · Answer 9 · answered Jun 25 '20 at 13:41

6

This fixed my problem

xhost +

but Be aware that xhost + completely deactivates authentication and allows everyone to access all application on your screen.

xhost +si:localuser:root seems to work similar with proper authentication.

answered Jun 25 '20 at 13:41

Bercove

987
10
18

score 4 · Answer 10 · answered Oct 28 '16 at 21:05

4

First: start XQuartz

Second: ssh -X user@ip_address

...: start your process

if you ssh and then start XQuartz you will get that error

answered Oct 28 '16 at 21:05

Aleks Tkachenko

704
7
6

N_E · Answer 11 · 2016-02-28T07:03:36.040

3

After several days of futile effort of installing glassfish on raspberry pi 2 with headless fedora 22, Below worked for me without a hitch

 unset DISPLAY
java -Djava.awt.headless=true -jar glassfissh-installer-v2ur2-b04-linux.jar

got my help from here

edited Feb 28 '16 at 07:03

answered Feb 27 '16 at 01:26

N_E

743
10
16

score 2 · Answer 12 · edited Apr 13 '17 at 14:50

2

I was using Xming and got similar error. Following steps were taken to fix the issue:

In Xming launch check the box no access control.
In putty ran the following command: DISPLAY=XXX.XXX.XXX.XX:0.0; export DISPLAY

Replace XXX.XXX.XXX.XX with your IP address.

edited Apr 13 '17 at 14:50

Vadim Kotov

8,084
8
48
62

answered Apr 13 '17 at 14:38

Shashank

29
1

I am in the same configuration, however it didn't work. I needed to add the IP executing X11 in X0.hosts file – Christophe Moine Dec 18 '18 at 12:48

score 2 · Answer 13 · answered Sep 05 '18 at 07:42

2

First do this either in Build Phase of Jenkins if using or set in /etc/profile:

unset DISPLAY
export DISPLAY=:0

then set this property either in java code or using maven: -Djava.awt.headless=false

answered Sep 05 '18 at 07:42

Pankaj Kumar Katiyar

1,474
1
20
36

score 2 · Answer 14 · answered Dec 05 '18 at 05:47

2

Solved. I just logout and login with xorg!

answered Dec 05 '18 at 05:47

Nilesh

2,054
3
23
43

1

export DISPLAY=:0 or export DISPLAY=:1 did not work for me. Logging out and logging in solved it for me. – Optimus Jan 07 '19 at 11:19

score 2 · Answer 15 · edited Jan 15 '23 at 03:43

2

check whether $DISPLAY variable is set or not, with the below command:

echo $DISPLAY

if the display variable is not set, run the below command to set, (even if it is set, you can have below one for your session)

export DISPLAY=:0.0

in putty also have the x display location as :0.0

edited Jan 15 '23 at 03:43

Ruslan López

4,433
2
26
37

answered Apr 23 '20 at 17:01

Naresh A

57
6

Koti Anekallu · Answer 16 · 2015-12-14T08:17:12.183

1

Michael-O gave useful approach to solve the problem. Another way to solve this is by starting the server with Putty Console.

edited Dec 14 '15 at 08:17

answered Dec 14 '15 at 08:11

Koti Anekallu

23
5

can you maybe explain a Little more how that would work? (I have never used putty) – mrk Dec 07 '18 at 18:36

score 1 · Answer 17 · answered Jan 02 '17 at 05:36

1

In my case there was no space left in my machine and I faced the same issue. Some times it could be the space issue. Check the space in your Linux/Unix environment and make sure your machine have enough space.

answered Jan 02 '17 at 05:36

user3016200

11
1

score 1 · Answer 18 · answered Feb 16 '18 at 19:15

1

For Ubuntu 17.10 Install X virtual frame buffer (xvfb)

apt install xvfb

And added these lines to the /etc/profile file...

# Start the X virtual frame buffer (Xvfb)
if [ -f /usr/X11R6/bin/Xvfb ]; then
/usr/X11R6/bin/Xvfb :1 -screen 0 1366x768x32
fi

# Set the DISPLAY variable for the X virtual frame buffer (Xvfb)
export DISPLAY=localhost:1.0

answered Feb 16 '18 at 19:15

cwilliamsz

718
9
20

3

Now I just get "Exception in thread "main" java.awt.AWTError: Can't connect to X11 window server using 'localhost:1.0' as the value of the DISPLAY variable." on Ubuntu 16.04. The Xvfb binary now seems to be located at /usr/bin, not /usr/X11R6/bin, but gives me "Couldn't add screen 0 (EE)". – Chris Jenks Mar 31 '18 at 00:31

score 1 · Answer 19 · answered Nov 01 '20 at 12:09

I had the same issue on the Linux server I was working on. Connecting java to a X11 display worked on the head node, but not on any other. After contacting the administrator, it turned out that the current version of our job-scheduling system (SLURM) did not support X11 forwarding. They had to update SLURM (newer versions of SLURM support it) for it to work.

score 0 · Answer 20 · answered Apr 24 '13 at 17:02

0

the only way i got it to work was running the script with a template. e.g. sudo ./glassfish-3.1.2.2-unix.sh -s template

This installs Glassfish in Silent Mode. http://docs.oracle.com/cd/E18930_01/html/821-2427/ghmva.html

answered Apr 24 '13 at 17:02

janex

497
4
14

score 0 · Answer 21 · answered May 02 '13 at 05:48

I run into the same error with you when i run the jconsole command at remote. I want to modify a parameter at jconsole that run on a remote Linux host, i can login the host use the secureCRT, the terminal throw this error information. Fortunately, when use the Putty, it's ok. Weird....

score 0 · Answer 22 · answered Nov 01 '13 at 16:15

0

If you see this error in Hudson, try to remove the .java directory from your home directory, it may work for you.

answered Nov 01 '13 at 16:15

user2945593

1
1

score 0 · Answer 23 · answered Oct 12 '15 at 11:16

0

If you start application on a remote server while logged in by ssh then another way would be to start ssh with -x parameter or add ForwardX11 no in your /etc/ssh/ssh_config. In this case ssh will not create environment variable DISPLAY.

answered Oct 12 '15 at 11:16

user3132194

2,381
23
17

score 0 · Answer 24 · answered Sep 13 '17 at 05:46

0

If you're triggering your code from Jenkins, enabling the option "Start Xvfb before the build, and shut it down after" might help. It helped me.

answered Sep 13 '17 at 05:46

Akshay Maldhure

787
2
19
38

score 0 · Answer 25 · answered Sep 20 '17 at 18:07

0

change to a another user and try except root. it works for me.

answered Sep 20 '17 at 18:07

Vinod Ranga

511
8
15

score 0 · Answer 26 · edited Jan 06 '18 at 22:39

0

I just didn't log out of root before running ./studio.sh All set.

edited Jan 06 '18 at 22:39

user207421

305,947
44
307
483

answered Jan 06 '18 at 21:41

Praveen Kumar Verma

2,988
2
18
31

score 0 · Answer 27 · answered Sep 04 '18 at 07:56

In my case this error was not related to the DISPLAY port. I was trying to load an XML into Windchill (a PLM-software) and received only the above error on the terminal. In a logfile I found the report that my XML-file was corrupt. Maybe someone has a similar problem and can use this answer.

Seff · Answer 28 · 2019-10-28T06:09:45.797

0

Mine issue was with the firewall. Disabled it temporarily.

[EDIT] And, the server hostname was pointing to another IP. Set it to simply localserver. strace xclock helped to debug this issue.

edited Oct 28 '19 at 06:09

answered Oct 28 '19 at 05:18

Seff

1,546
1
17
19

score 0 · Answer 29 · answered Feb 25 '20 at 09:38

0

I have fixed this issue by logging in using Xorg. By default, I have used Wayland. It looks like Wayland eliminates most of the design flaws of the Xorg it has its own issues.

answered Feb 25 '20 at 09:38

Easwer A.P

19
1
10

score 0 · Answer 30 · edited Sep 14 '20 at 15:22

0

For me none of the above worked, but after long search this worked for me.

export DISPLAY=localhost:20.0

edited Sep 14 '20 at 15:22

DanielM

3,598
5
37
53

answered Sep 14 '20 at 13:44

veer

123
1
9

score 0 · Answer 31 · answered Apr 12 '22 at 12:45

0

export localhost:1
-Djava.awt.headless=true

answered Apr 12 '22 at 12:45

Dhammadip

87
1
4

score 0 · Answer 32 · answered Feb 22 '23 at 14:11

In my case I have this exact error when I was launching the Jetbrains IDEs, such as Pycharm, IntelliJ IDEA...

I typed this in the same terminal that I was using to start the IDE to solve the problem:

export DISPLAY=:1

Then I started the IDE from the same terminal issuing the command pycharm and it worked like a charm.

The output of both IDEs was:

score 0 · Answer 33 · answered Jul 12 '23 at 09:18

0

run below cmd fixed my issue. works for my case

unset DISPLAY

answered Jul 12 '23 at 09:18

ybdesire

1,593
1
20
35

score -1 · Answer 34 · edited Nov 01 '16 at 15:01

-1

For me, the problem was that xorg-x11-xauth wasn't installed. I installed it and then it worked.

The packages that I have now are:

libX11-common-1.6.3-2.el6.noarch
libX11-1.6.3-2.el6.i686
libX11-1.6.3-2.el6.x86_64
xorg-x11-drv-ati-firware-7.6.1-2.el6.noarch
xorg-x11-xauth-1.0.9-1.el6.x86_64

edited Nov 01 '16 at 15:01

agc

7,973
2
29
50

answered Nov 01 '16 at 14:19

Kwokman Chung

1

Java Can't connect to X11 window server using 'localhost:10.0' as the value of the DISPLAY variable

34 Answers34

Linked

Related