[GRASSLIST:2197] Re: d.mon socket problem

[Scott Mitchell]

If the simple test is true - that X11 is running, then I'd suggest 
starting GRASS from an xterm (labelled "Terminal" in the Applications 
menu if you're using Apple's X11) instead of from the Terminal 
application, because then you know that the environment is set up for 
X11.

This can be slightly confusing because Apple has the Terminal 
application, which by itself is not X11 aware, but then Apple also 
calls xterms inside X11 "Terminal".  But they are not the same.  You 
CAN make X11 software work from the Terminal.app prompt, but it 
eliminates a possible source of error/confusion if you keep everything 
within the X11 Server windows.

If you are already trying this from an xterm (or maybe you know all 
this already, if so then sorry), or even if you have specific good 
reasons to not start GRASS from within X11, then the next step is to 
ensure that other X11 programs can create new windows - e.g. if, at the 
prompt, you enter xterm& as a command, does another window with a shell 
prompt start up ?

If not, then it is an X11 problem, and it's pretty safe to say the 
error has nothing to do with GRASS per se.  You need to get a working 
X11 environment to be able to display GRASS monitors using the standard 
GRASS distribution.  Probably the x11-users list hosted by Apple or the 
X-Unix mailing list would be more useful than this one to get this 
problem fixed, although I (or others here) might be able to help, too.

If other X11 applications have no trouble but GRASS still can't open a 
monitor, this list is definitely the place to be.  It would be odd if 
the install process hadn't created the sockets and configuration files 
needed to start up a GRASS monitor, but.... ?

If "you know all this" still applies, I apologize, but more details are 
needed about your setup.

Cheers,
Scott

On Monday, Jan 12, 2004, at 15:29 Canada/Eastern, Roger Bivand wrote:

> On Mon, 12 Jan 2004, Ben Logan wrote:
>
>> On Mon, Jan 12, 2004 at 11:27:36AM -0600, William K wrote:
>>> make sure you have the DISPLAY environment var set to :0.0
>>>
>>> also make sure X11 is already running, if you're running GRASS from 
>>> the
>>> Terminal instead of an X11 xterm.
>>>
>>> On Jan 12, 2004, at 10:16 AM, David Orme wrote:
>>>
>>>> Hi,
>>>>
>>>> I've got grass57 built now - thanks to everyone. When I try and 
>>>> start
>>>> a graphics monitor i get the following (most recent weekly snapshot,
>>>> Mac OS 10.2.8):
>>>>
>>>>> GRASS
>>>>> 5.7.-cvs:/usr/local/src/grass57_exp_2004_01_10/bin.powerpc-apple-
>>>>> darwin6.8 > d.mon start=x0
>>>>> ERROR: Graph_Set: can't open Display
>>>>> No socket to connect to for monitor <x0>.
>>>>> Problem selecting x0. Will try once more
>>>>> No socket to connect to for monitor <x0>.
>>
>> David,
>>
>> I don't know anything about the Mac OS, but my understanding is that
>> it is very unixish.  If that's true, in addition to William's
>> suggestions, you might make sure you have permission to write to
>> wherever GRASS is trying to create the sockets.  For example, on my
>> Linux box, sockets for user "ben" are created in /tmp/grass-ben.  If
>> "ben" didn't have write permissions on /tmp, no socket(s) could be
>> created.
>
> There has been discussion on this recently on the R list. While OSX is
> close to Unix, it isn't always right to think Unix means X. R users 
> have
> found that OSX will only sometimes set DISPLAY (so causing graphics 
> output
> to fail when needing a running X server - Apple provides alternatives I
> think). The cases were predictable. Google "R" gets you to R, R-help
> mailing list archives.
>
> Roger
>
>>
>> Regards,
>> Ben
>>
>>
>
> -- 
> Roger Bivand
> Economic Geography Section, Department of Economics, Norwegian School 
> of
> Economics and Business Administration, Breiviksveien 40, N-5045 Bergen,
> Norway. voice: +47 55 95 93 55; fax +47 55 95 93 93
> e-mail: Roger.Bivand at nhh.no
>
------
Scott W. Mitchell		Scott_Mitchell at carleton.ca
Department of Geography and Environmental Studies
Carleton University, B349 Loeb Building
Ottawa, ON Canada
+1-613-520-2600 ext 2695