From owner-freebsd-bugs  Mon Oct  6 21:00:11 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id VAA22860
          for bugs-outgoing; Mon, 6 Oct 1997 21:00:11 -0700 (PDT)
          (envelope-from owner-freebsd-bugs)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA22816;
          Mon, 6 Oct 1997 20:59:57 -0700 (PDT)
          (envelope-from jkh@FreeBSD.org)
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Received: (from jkh@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id UAA29738;
	Mon, 6 Oct 1997 20:59:31 -0700 (PDT)
Date: Mon, 6 Oct 1997 20:59:31 -0700 (PDT)
Message-Id: <199710070359.UAA29738@freefall.freebsd.org>
To: charlesr@cftnet.com, jkh@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/4716
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Synopsis: Unable to  run  fvwm .  Program  cannot open  'Display'.

State-Changed-From-To: open-closed
State-Changed-By: jkh
State-Changed-When: Mon Oct 6 20:58:51 PDT 1997
State-Changed-Why: 
This is likely not a problem with fvwm so much as the user
not starting X with the proper scripts.  "man startx" and
go from there.