This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 4763 - xinit Can Fail If 'stty tostop' In Use On Console
xinit Can Fail If 'stty tostop' In Use On Console
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-08-27 22:59 EDT by Jason Bucata
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-08-29 12:08:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jason Bucata 1999-08-27 22:59:07 EDT
I encountered this bug when I decided to use 'stty tostop'
on my console window.  I get warning messages printed to my
console whenever I start X to the effect that fvwm wasn't
found and that it's resorting to twm to get me going.  (I
have yet to care about that, since I like twm fine enough.)
It turns out that this message apparently causes xinit to
hang when starting in a console with tostop set.

I'll mail my patch to startx to turn off tostop before and
restore the original stty settings after xinit runs.
Comment 1 Preston Brown 1999-08-29 12:08:59 EDT
you can fix the fvwm issue by upgrading to the errata release of the
'xinitrc' package in

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