Thanks for the hints on this, I've managed to get it working without
the warning message. Here's what I did:
bash$ xauth
xauth add :0 . hexnumber # I used FACEFEEDFACEFEED
xauth add localhost:0 . hexnumber
xauth exit
my .ssh/config has:
ForwardX11Trusted yes
XAuthLocation /usr/bin/xauth
I updated to xwin 6.7.0.0-8 last night after hoping to pick up a few bug
fixes, and notice that the escape sequences used to change the window title
don't work at all (in some windows), or work once (in some other windows),
or don't work at all (in still others).
The .tcshrc/.bashrc haven't
References: [EMAIL PROTECTED]
Reply-to: cygwin-xfree at cygwin dot com
On Thu, 6 May 2004, Benn Schreiber wrote:
I updated to xwin 6.7.0.0-8 last night after hoping to pick up a few
bug
fixes, and notice that the escape sequences used to change the window
title
don't work at all (in some
2004 13:43:50 -0400 (EDT)
Subject: Re: Odd effect with xwin 6.7.0.0-8
References: [EMAIL PROTECTED]
Reply-to: cygwin-xfree at cygwin dot com
On Thu, 6 May 2004, Benn Schreiber wrote:
I updated to xwin 6.7.0.0-8 last night after hoping to pick up a few
bug
fixes, and notice that the escape
I just upgraded my system to the latest XFree (4.3.0-4, I believe). In my
startxwin I had an xset fp+ to add the truetype fonts directory to the font
path (which I never got working...perhaps this is a hint, but...)
With the latest bits the Xserver core dumps shortly after the xset fp+
happens.
Did you have to run ttmkfdir (or whatever it is called) at any point?
Harold
Yes, I have run both ttmkfdir and mkfontdir in the directory. Interestingly,
if I do the xset after the window manager is up (as best I can correlate
it), it works fine. But, if I do it in startxwin, the font element
Got it. Need to run ttmkfdir BEFORE mkfontdir (doh). I'm going back to bed.
Thanks for the kick in the right direction.
Benn
-Original Message-
From: Benn Schreiber [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 3:20 PM
To: '[EMAIL PROTECTED]'
Subject: Re: xset add to font
