there is one thing I forgot. You have to issue the following in the
terminal connected to XServer

xhost localhost

this will allow the connections to XServer from localhost only.
For troubleshooting (not to be permanent) you can do:

xhost +

this turns off any restrictions.
If you still have a problem, check if port 6000 is open:

netstat -nal | grep 6000

if not, very likely you have to go double check the original instructions.


--pawel



On Fri, Dec 28, 2012 at 6:15 PM, <suter_dan...@hotmail.com> wrote:

> Hi Pawel,
>
> Thanks for your suggestion but I still got the same problem (after I
> enabled tcp connections). I don't know how to debug this problem.
>
> cheers
>
> Am Freitag, 28. Dezember 2012 17:11:00 UTC+1 schrieb Pawel Jasinski:
>>
>> hi,
>>
>> can it be that you need to enable tcp connection to your xserver?
>> http://askubuntu.com/**questions/72812/how-to-**disable-nolisten<http://askubuntu.com/questions/72812/how-to-disable-nolisten>
>>
>> cheers,
>> pawel
>>
>>
>> On Fri, Dec 28, 2012 at 3:31 PM, <suter_...@hotmail.com> wrote:
>>
>>> My tests on jenkins are failing because jenkins can't connect to the x
>>> server on my ubuntu machine. The machine disposes of a display, so it's not
>>> headless.
>>>
>>> I tried to set the connection settings on the etc/init.d/jenkins
>>> configuration as follows:
>>>
>>> #Display connection
>>>> export DISPLAY=:0.0
>>>
>>>
>>> In my pom.xml:
>>>
>>>>  <plugin>
>>>> <groupId>org.apache.maven.**plugins</groupId>
>>>> <artifactId>maven-surefire-**plugin</artifactId>
>>>>  <version>2.5</version>
>>>> <configuration>
>>>> <systemPropertyVariables>
>>>>  <java.awt.headless>false</**java.awt.headless>
>>>> </systemPropertyVariables>
>>>> </configuration>
>>>>  </plugin>
>>>
>>>
>>> The error message is the following:
>>>
>>>> Can't connect to X11 window server using ':0.0' as the value of the
>>>> DISPLAY variable.
>>>
>>>
>>> I tried to launch a x server from the console using startx but it says
>>> it's already running. So this does not seem to be the problem.
>>>
>>
>>

Reply via email to