Charles Wilson wrote:
Lothar Brendel wrote:
It should list, but it doesn't:
$ grep -A9 '@ run2' setup-2.ini
^^^
This was the clue.
As it happens, the union mount stuff had an override for setup.hint,
but not the entire directory. So, the
Lothar Brendel wrote:
Unfortunately the situatiuon with ``startxwin.bat'' is worse now:
* ``checkX -t 12'' still doesn't wait (?!?)
I can't reproduce this.
* After again inserting a sleep between checkXing and starting the
xterm, the latter is marginally successful: The process is shown as
On 11/25/2009 8:18 AM, Charles Wilson wrote:
Lothar Brendel wrote:
* After again inserting a sleep between checkXing and starting the
xterm, the latter is marginally successful: The process is shown as
running but no xterm is showing up :-(
That's an xterm/XWin issue.
And it's been
Jon TURNEY wrote:
This is typical of the current issue we have where 'run xterm' blocks when
xterm tries to output 'Warning: Missing charsets in String to FontSet
conversion'
Any one of:
- installing the CJK fonts
- having 'tty' in the CYGWIN environment variable
- having the LANG
On 11/25/2009 9:57 AM, Charles Wilson wrote:
Jon TURNEY wrote:
This is typical of the current issue we have where 'run xterm' blocks when
xterm tries to output 'Warning: Missing charsets in String to FontSet
conversion'
Any one of:
- installing the CJK fonts
- having 'tty' in the CYGWIN
I'm trying to get a remote desktop to come up, but am not sure what's
required on the remote end.
Locally, I've been trying 'Xwin -query hostname
Either they come up with no login screen, or in one case an error
where it said:
winProcEstablishConnection - Xdmcp, waiting to start clipboard
If you're running the beta, try adding -extension Composite -noclipboard
Linda Walsh wrote:
I'm trying to get a remote desktop to come up, but am not sure what's
required on the remote end.
Locally, I've been trying 'Xwin -query hostname
Either they come up with no login screen, or in one
Charles Wilson wrote:
Lothar Brendel wrote:
Unfortunately the situatiuon with ``startxwin.bat'' is worse now:
* ``checkX -t 12'' still doesn't wait (?!?)
I can't reproduce this.
Stupid me, sorry. When updating to pull in libustr1, run2 was accidently
reverted to 0.3.0-1.
* After again
