Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!mcnc!thorin!alanine.cs.unc.edu!leech
From: leech@alanine.cs.unc.edu
Newsgroups: comp.windows.x
Subject: Various problems with X on DECstation 3100s
Message-ID: <7977@thorin.cs.unc.edu>
Date: 30 Apr 89 00:49:55 GMT
Sender: news@thorin.cs.unc.edu
Reply-To: leech@alanine.cs.unc.edu ()
Organization: University Of North Carolina, Chapel Hill
Lines: 26
Expires:
References:
Sender:
Followup-To:
Keywords:


    When the DEC 'dxsession' program runs my .X11Startup file, any
error messages produced don't show up in the messages window. This
makes debugging the shell script very difficult. Is there some way to
get output from .X11Startup captured?

    DEC's version of xterm claims to recognize (e.g. xterm -help) the
'-C' option to capture console output, but when the option is actually
given, it is not recognized. Is there any other way to get console
output in an xterm window?

    Finally, we've seen some very strange behavior from the 3100 X
server.  After killing the DEC window manager 'dxwm' and replacing it
with uwm or twm (as required for the sanity of most users), moving a
window sometimes leaves behind a residue which overlaps all other
contents of the original window location. This residue cannot be
disposed of by having the window manager refresh the screen, or
changing the root bitmap - only logging off will get rid of it. This
is a severe problem, apparently with the server. Any fixes/workarounds?

    Thanks!
--
    Jon Leech (leech@cs.unc.edu)    __@/
UNDERWHELMING OFFER OF THE MONTH:
    "Please feel free to skip the payment on this month's statement.
     Normal finance charges will apply." - NCNB VISA