From owner-freebsd-bugs  Tue Oct  7 00:30:04 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id AAA05633
          for bugs-outgoing; Tue, 7 Oct 1997 00:30:04 -0700 (PDT)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id AAA05626;
          Tue, 7 Oct 1997 00:30:01 -0700 (PDT)
          (envelope-from gnats)
Date: Tue, 7 Oct 1997 00:30:01 -0700 (PDT)
Message-Id: <199710070730.AAA05626@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: j@uriah.heep.sax.de (J Wunsch)
Subject: Re: bin/4716: Unable to  run  fvwm .  Program  cannot open  'Display'.
Reply-To: j@uriah.heep.sax.de (J Wunsch)
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/4716; it has been noted by GNATS.

From: j@uriah.heep.sax.de (J Wunsch)
To: charlesr@cftnet.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/4716: Unable to  run  fvwm .  Program  cannot open  'Display'.
Date: Tue, 7 Oct 1997 08:56:25 +0200

 As charlesr@cftnet.com wrote:
 
 > After installing  2.2.2 and  configuring X11 stuff, I tried to run some
 > of the windows managers, in particular fvwm. The error message I  get is
 > the manager cannot open the display.
 
 Well, then you most likely don't have your $DISPLAY set correctly (for
 whatever reason, you didn't tell us much about your exact steps how to
 start fvwm, or even the X server at all).
 
 This looks like something to be asked on freebsd-questions@freebsd.org,
 but not like a valid bug report.
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)