RE: Warning: No xauth data
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
Next, I have a little macro in .bashrc:
startapp() { (ssh -Xn $* ) ; }
declare -fx startapp
Then, to start a remote application (xterm in this case) I do:
bash$ startapp othernode xterm
I haven't done exhaustive testing, but seems to do the trick.
By the way, the new Cygwin/X bits are GREAT! Thank you for the great update!!!
Benn
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Odd effect with xwin 6.7.0.0-8
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 changed, but the behavior has definitely changed (and not for the better) with the latest couple of xwin versions. I hope the previous behavior can be restored. Cygwin and Cygwin-XFree are great tools. Thanks
Re: Odd effect with xwin 6.7.0.0-8
Yes, I'm using xterm, and yes, they seem to work...sometimes, but not reliably. Thanks From: Alexander Gottwald alexander dot gottwald at s1999 dot tu-chemnitz dot de To: cygwin-xfree at cygwin dot com Date: Thu, 6 May 2004 18:56:23 +0200 (MEST) 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 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). They work in xterm. bye ago
Re: Odd effect with xwin 6.7.0.0-8
Thanks, Rob. I noticed after I first posted that sometimes it works after a restart. But, I NEVER saw this problem with earlier builds, so (prematurely) concluded that it was new with this one. Benn From: Rob Foehl rwf at loonybin dot net To: cygwin-xfree at cygwin dot com Date: Thu, 6 May 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 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). Try restarting XWin.exe. That's happened to me on a number of occasions (with different builds, spanning a few months' time).. Can't explain it, but it's a minor annoyance. -Rob
xset add to font path kills Xserver
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. So, two questions, which hopefully someone can easily answer: 1) Have you successfully added truetype fonts to your font path? If so, how?\ 2) Failing at 1), has anyone else observed this problem with 4.3.0-4? Thanks Benn
Re: xset add to font path kills Xserver
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 does not get added to the path, and then XWin dies. I'm going to try the XF86Config route. Thanks for the suggestions! If you have any others, or if there are any tests I can do that might be useful, I'm game. Benn
FW: Re: xset add to font path kills Xserver
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 path kills Xserver 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 does not get added to the path, and then XWin dies. I'm going to try the XF86Config route. Thanks for the suggestions! If you have any others, or if there are any tests I can do that might be useful, I'm game. Benn
