delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/02/04/17:15:12

From: dcm AT ni DOT nacs DOT net
Subject: Re: Problem with `window manager already running' X-windows error
4 Feb 1998 17:15:12 -0800 :
Message-ID: <19980204143428.39168.cygnus.gnu-win32@ni.nacs.net>
References: <199802040840 DOT IAA103548 AT out1 DOT ibm DOT net>
Reply-To: dcm AT ni DOT nacs DOT net
Mime-Version: 1.0
To: gnu-win32 AT cygnus DOT com

On Wed, Feb 04, 1998 at 08:40:36AM +0000, vischne AT ibm DOT net wrote:
> Someone recently posted to this conference about starting up X-windows
> and getting a `window manager already running' message when fvwm was
> supposed to come up.

That's because most X-servers for Windows come with a built-in WM, usually
a twm-clone, which needs to be disable.  Then they need to edit their 
local xinitrc, or whatever starts the Xserver locally, and start their
WM of choice, which in this case seems to be fvwm95-2.

> I think that is the result of optimism and not buying books on how to
> run X-windows. Somewhere in the /var/... directory of Linux is the
> xinitrc file that is a bash script for starting X-windows when startx
> is called.  I imagine that c:\var\.... is similarly burdened when X-
> windows/cygwin runs under Windows 95/NT.  There is a very good chance
> that the person who posted the problem actually _does_ have another
> window manager running, and checking the xinitrc script will verify
> this.  Editing the script to delete the other window manager in favor
> of fvwm (or better, fvwm95-2) will remedy the problem.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019