* Manoj Srivastava <[EMAIL PROTECTED]> [050917 07:51]:
> At first blush, this does not appear to actually be a bug in
> fvwm: note that fvwm detects another version of fvwm running, so it
> does to window manager detection.
I'm not fluently enough in X specifications, but I get the same
behaviour also with sarge's fluxbox, blackbox, ion3, xfwm4, wmaker
and twm, thus with every window manager (other than fvwm itself) I have
tried so far and a majority of all window managers available in Debian.
Also note that this is a regression, as woody's fvwm2 does not have this
problem, but correctly outputs:
[FVWM][CatchRedirectError]: <<ERROR>> another WM is running
This message is still in the current fvwm code, but seems not to get
triggered for reasons I do not understand.
When sarge's fvwm is running woody's fvwm prints:
[FVWM][SetupICCCM2]: <<ERROR>> another ICCCM 2.0 compliant WM is running, try
-replace
Also note that all other WMs are able to detect each other, and even
refuse to run when the (alleged?) buggy fvwm is running.
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
