Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 82998 - xterm -wf doesn't wait for map
Summary: xterm -wf doesn't wait for map
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 8.0
Hardware: i586
OS: Linux
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-01-29 13:32 UTC by Ian Collier
Modified: 2007-04-18 16:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-01-29 13:39:53 UTC

Attachments (Terms of Use)

Description Ian Collier 2003-01-29 13:32:50 UTC
Description of problem:
The "-wf" option as documented in the xterm manual page doesn't work.

Version-Release number of selected component (if applicable):
XFree86-4.2.0-72, although this is a problem on all releases of
Red Hat from 6 onwards (but my 5.1 box works fine).

How reproducible:

Steps to Reproduce:
1. Use a window manager (such as fvwm) which allows interactive
   placing of new windows
2. type: xterm -wf -e sh -c 'sleep 5;echo hello;sleep 5'
3. wait 8 seconds before placing the new window.
Actual results:
The new window already says "hello" and quickly disappears.

Expected results:
The new window should be blank for five seconds, then say "hello"
and remain for five further seconds.

Additional info:
This can be fixed by using the flag -DUSE_HANDSHAKE while compiling

Comment 1 Mike A. Harris 2003-01-29 13:39:53 UTC
Please report this directly to for attention of the
xterm maintainer.  If this is something that needs to be fixed, he is the
one best suited to determine the proper fix and get it into XFree86 CVS
in time for 4.3.0.

We provide xterm only for convenience as it is a historical legacy
application some users prefer.  We do not directly support it however.

Note You need to log in before you can comment on or make changes to this bug.