Re: checkX problems
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 tarballs themselves magically showed up in the release-2 area when I installed them in the release/ area, but release-2 retained the old setup.hint. Fixed. ACK. libustr1 was pulled in now. Unfortunately the situatiuon with ``startxwin.bat'' is worse now: * ``checkX -t 12'' still doesn't wait (?!?) * 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 :-( I really would investigate this further, but I only get diagnostic output from ``checkX'' (--verbose or --debug) when running it from within an xterm, and that's obviously pointless. Thus, how to obtain output from ``checkX`` in Windows' Command Prompt, how to get it in Cygwin's bash window? Asks Lothar -- 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/
Re: checkX problems
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 running but no xterm is showing up :-( That's an xterm/XWin issue. I really would investigate this further, but I only get diagnostic output from ``checkX'' (--verbose or --debug) when running it from within an xterm, and that's obviously pointless. Thus, how to obtain output from ``checkX`` in Windows' Command Prompt, how to get it in Cygwin's bash window? checkX --notty --debug -t 12 -- Chuck -- 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/
Re: checkX problems
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 discussed in several recent threads. A summary of workarounds can be found in http://cygwin.com/ml/cygwin-xfree/2009-11/msg00174.html Ken -- 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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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 environment set to a non-UTF-8 locale should work around this problem Note that the environment variable will have to be set via the system applet in the Windows control panel, as only that controls the environment for the startxwin.bat started from the start menu... There's another option. In startxwin.bat, you could use run2.exe instead of run. Instead of: %RUN% bash -l -c XWin -multiwindow -clipboard -silent-dup-error Use %RUNTWO% /usr/bin/XWin.xml where XWin.xml is something like the following (untested): ?xml version=1.0 encoding=us-ascii? Run2Config xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=run2.xsd SelfOptions / Global Environment !-- either of these, or both, and modified as desired -- Set var=LANG value=C.ASCII/ Append var=CYGWIN value= tty/ /Environment Target filename=/usr/bin/bash.exe startin=~ Arg-l/Arg Arg-c/Arg ArgXWin -multiwindow -clipboard -silent-dup-error/Arg /Target /Global /Run2Config -- Chuck -- 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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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 environment variable - having the LANG environment set to a non-UTF-8 locale should work around this problem Note that the environment variable will have to be set via the system applet in the Windows control panel, as only that controls the environment for the startxwin.bat started from the start menu... There's another option. In startxwin.bat, you could use run2.exe instead of run. Instead of: %RUN% bash -l -c XWin -multiwindow -clipboard -silent-dup-error Use %RUNTWO% /usr/bin/XWin.xml where XWin.xml is something like the following (untested): ?xml version=1.0 encoding=us-ascii? Run2Config xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=run2.xsd SelfOptions / Global Environment !-- either of these, or both, and modified as desired -- Set var=LANG value=C.ASCII/ Append var=CYGWIN value= tty/ /Environment Target filename=/usr/bin/bash.exe startin=~ Arg-l/Arg Arg-c/Arg ArgXWin -multiwindow -clipboard -silent-dup-error/Arg /Target /Global /Run2Config You can also just use the DOS set command right in startxwin.bat. In the case of CYGWIN, the syntax would be SET CYGWIN=%CYGWIN% tty Ken -- 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/
remote desktop
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 client until 4th call... winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winGetDisplay: DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcQueryTree - Hello winProcQueryTree - Clipboard client already launched, returning. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winDeinitMultiWindowWM - Noting shutdown in progress --- Is there something I'm missing or need to setup on my remote clients? They are various levels of suse boxen, and claim to have 'xdm' enabled via their chkconfig -- but I don't know if they are configured properly. Think was, is that I tried this before, and it just worked, but after some recent updates, it stopped working. I guess I just got lucky with it working before? It may be there's too little to go on here, and I just need to start from scratch, and try to figure out how XDM works from the man page, but it's odd that it was setup to 'work', but just seems to have randomly broke as I wasn't trying to change any configuration related to xdm on the remote machines...*sigh*. thanks if anyone sees any overt problems or knows any common ones w/suse... linda -- 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/
Re: remote desktop
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 case an error where it said: winProcEstablishConnection - Xdmcp, waiting to start clipboard client until 4th call... winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winGetDisplay: DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcQueryTree - Hello winProcQueryTree - Clipboard client already launched, returning. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winDeinitMultiWindowWM - Noting shutdown in progress --- Is there something I'm missing or need to setup on my remote clients? They are various levels of suse boxen, and claim to have 'xdm' enabled via their chkconfig -- but I don't know if they are configured properly. Think was, is that I tried this before, and it just worked, but after some recent updates, it stopped working. I guess I just got lucky with it working before? It may be there's too little to go on here, and I just need to start from scratch, and try to figure out how XDM works from the man page, but it's odd that it was setup to 'work', but just seems to have randomly broke as I wasn't trying to change any configuration related to xdm on the remote machines...*sigh*. thanks if anyone sees any overt problems or knows any common ones w/suse... linda -- 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/ -- 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/
Re: checkX problems
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 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. Errh, yes. Hence, to make Cygwin/X+xterm run out of the box (using the start menu shortcut), you have to install the CJK fonts. One more noob-question, sorry: Which font-package does provide the CJK fonts? I tried several ones but up to now in vain. Ciao Lothar -- 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/
