nanogui: Thread: Question 2: cannot run nano-X on X11...

Hello,
here is my second question:
With the Configs/config.x11 as configuration file I can run only microwindows demos, and
not nano-x applications. It refuses to connect to nano-X with the following errors:

> Cannot bind to named socket
> nxclient: retry connect attempt 1
> nxclient: retry connect attempt 1
> ...
> nxclient: retry connect attempt 10
> Couldn't connect to Nano-X server!
> nxclient: retry connect attempt 10
> cannot open graphics

My host is SuSE 9.2 Professional, with gcc (GCC) 3.3.4 (pre 3.3.5)
I am using X11 and KDE as WindowManager and Desktop Environment.

Here is my step to obtain a correct build:
1- goto in src directory (cd src)
2- cp Configs/config.x11 config
3- make (...wait...)
4- su (changing to super user just to install)
5- make install
6- turn back to normal user and launch ( ./demo2.sh )

Any hint, help, clue?

Best regards,
-- 
Gianluca Renzi
Eptar s.r.l.
Via Celletta 8/B
40026 Imola (BO) ITALY
Tel.:	+39-0542-609060
Fax.:	+39-0542-609054

This may sound like a silly question, but is nano-X actually running ?
i.e. run ./nano-X -p then ./demo2.sh

>>> Gianluca ####@####.#### 19/10/06 15:24 >>>
Hello,
here is my second question:
With the Configs/config.x11 as configuration file I can run only microwindows demos, and
not nano-x applications. It refuses to connect to nano-X with the following errors:

> Cannot bind to named socket
> nxclient: retry connect attempt 1
> nxclient: retry connect attempt 1
> ...
> nxclient: retry connect attempt 10
> Couldn't connect to Nano-X server!
> nxclient: retry connect attempt 10
> cannot open graphics

My host is SuSE 9.2 Professional, with gcc (GCC) 3.3.4 (pre 3.3.5)
I am using X11 and KDE as WindowManager and Desktop Environment.

Here is my step to obtain a correct build:
1- goto in src directory (cd src)
2- cp Configs/config.x11 config
3- make (...wait...)
4- su (changing to super user just to install)
5- make install
6- turn back to normal user and launch ( ./demo2.sh )

Any hint, help, clue?

Best regards,
-- 
Gianluca Renzi
Eptar s.r.l.
Via Celletta 8/B
40026 Imola (BO) ITALY
Tel.:	+39-0542-609060
Fax.:	+39-0542-609054

---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.#### 
For additional commands, e-mail: ####@####.#### 


-------------------------------------------------------------------------------------------


***** REDUCE WASTE! PLEASE DO NOT PRINT THIS EMAIL UNLESS ABSOLUTELY NECESSARY *****

This Email is intended only for the person(s) to whom it is addressed and may contain confidential information. If you have received this Email in error, please notify the sender and destroy any copies.

The content of this Email may not represent the views of Energy Technology and Control Ltd.

This Email has been scanned for viruses by Sophos Antivirus and is believed to be virus-free. 

Energy Technology and Control Ltd
25 North Street
Lewes
East Sussex
BN7 2PE
UK

Tel: +44 1273 480667

Email: ####@####.####

####@####.####

On Thursday 19 October 2006 18:17, Darren Legge wrote:
> > With the Configs/config.x11 as configuration file I can run only microwindows demos, and
> > not nano-x applications. It refuses to connect to nano-X with the following errors:
> 
> > Cannot bind to named socket
> > nxclient: retry connect attempt 1
> > nxclient: retry connect attempt 1
> > ...
> > nxclient: retry connect attempt 10
> > Couldn't connect to Nano-X server!
> > nxclient: retry connect attempt 10
> > cannot open graphics
> 
> This may sound like a silly question, but is nano-X actually running ?
> i.e. run ./nano-X -p then ./demo2.sh
It is not a silly question: it's a perfectly reasonable one.
Here is the demo2.sh script:

bin/nano-X & bin/nanowm & bin/nxterm & bin/nxeyes & bin/tux & sleep 10000

So, as you can see nano-X is the first command invoked by the script.

It returns this if launched from a cli:
$> bin/nano-X
Cannot bind to named socket

So it fails immediately.

How can I proceed further?

Best regards,
-- 
Gianluca Renzi

The nano-X FAQ states:
-------
One thing that will cause this error is the inability to create (or delete) the named socket "/tmp/.nano-X". You may have problems with this if one user creates the socket and then nano-X subsequently crashes if you try to run nano-X from another userid you will get this error. 
Delete the named socket "/tmp/.nano-X" if it exists, otherwise verify that the userid that is attempting to run nano-X has write permissions to the /tmp directory. 
-------
Also, you may look at your configuration file and see if your keyboard and mouse are properly configured and the proper devices are available.
You need to get nano-X working first.

Martin


-----Original Message-----
From: Gianluca ####@####.####
Sent: Friday, October 20, 2006 1:08 AM
To: ####@####.####
Cc: Darren Legge
Subject: Re: [nanogui] Question 2: cannot run nano-X on X11...


On Thursday 19 October 2006 18:17, Darren Legge wrote:
> > With the Configs/config.x11 as configuration file I can run only microwindows demos, and
> > not nano-x applications. It refuses to connect to nano-X with the following errors:
> 
> > Cannot bind to named socket
> > nxclient: retry connect attempt 1
> > nxclient: retry connect attempt 1
> > ...
> > nxclient: retry connect attempt 10
> > Couldn't connect to Nano-X server!
> > nxclient: retry connect attempt 10
> > cannot open graphics
> 
> This may sound like a silly question, but is nano-X actually running ?
> i.e. run ./nano-X -p then ./demo2.sh
It is not a silly question: it's a perfectly reasonable one.
Here is the demo2.sh script:

bin/nano-X & bin/nanowm & bin/nxterm & bin/nxeyes & bin/tux & sleep 10000

So, as you can see nano-X is the first command invoked by the script.

It returns this if launched from a cli:
$> bin/nano-X
Cannot bind to named socket

So it fails immediately.

How can I proceed further?

Best regards,
-- 
Gianluca Renzi

---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####

On Friday 20 October 2006 17:55, Martin Kajdas wrote:
> One thing that will cause this error is the inability to create (or delete) the named socket "/tmp/.nano-X". You may have problems with this if one user creates the socket and then nano-X subsequently crashes if you try to run nano-X from another userid you will get this error. 
> Delete the named socket "/tmp/.nano-X" if it exists, otherwise verify that the userid that is attempting to run nano-X has write permissions to the /tmp directory. 
This was the cause.

Thank you
---
Gianluca Renzi