Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!EU.net!Germany.EU.net!gomel.knirsch.de!knobel.knirsch.de!knobel.knirsch.de!andreas From: andreas@knobel.knirsch.de (Andreas Klemm) Newsgroups: comp.os.386bsd.questions Subject: Re: XOpenDisplay failures Date: 12 Jun 1994 16:19:40 GMT Organization: @ $HOME, 41469 Neuss, Germany Lines: 28 Message-ID: <2tfcje$fk@knobel.knirsch.de> References: <771348887snz@helen.demon.co.uk> NNTP-Posting-Host: knobel.knirsch.de X-Newsreader: TIN [version 1.2 PL2] Ian Newham (ian@helen.demon.co.uk) wrote: : I'm running NetBSD-current, 5th March ...not so current:) with XFree86 2.00 : I've recently tried compiling a few things, eg ghostscript, but they : all seem to fail with a Cannot Open Display ':0.0' or similar message : All the binaries that came with xfree are fine, they run ok. : I have noticed though that I managed to build gtetris4 ok, but that : calls XrmInitialize() then XOpenDisplay(), whereas those that fail : go straight in with XOpenDisplay(0). Have I got to rewrite everything : open the display with XrmInitialize first? Is there something dumb I'm : missing here (more than likeley)- I'm OK on unix but I don't : know much about X. Perhaps try to set the DISPLAY variable to "hostname:0.0" instead of only ":0.0" ?! The same message you get in a running X11 environment, when doing a `su` to become root. Then the DISPLAY variable isn't set anymore. Then you have to do a setenv DISPLAY hostname:0.0 before calling X11 programs. Andreas /// -- Andreas Klemm /\/\____ Wiechers & Partner Datentechnik GmbH andreas@knobel.knirsch.de ___/\/\/ andreas@wupmon.wup.de (Unix Support)