RE: Multiple XWin.exe programs loading and no xterm
On Fri, 8 Apr 2005, Phil Betts wrote: IIRC, there was talk a while back of making the multiwindow manager an external client. I don't know if anythng has been done in this direction, but if this were done, there would at least be a consistent startup for all WMs. There is an external MWWM client, but, IIRC, it doesn't work too well ATM. Kensuke would be the best person to talk about it, I guess... An alternative that I've not seen raised before: I was wondering if it would be possible to run XWin as a Windows service (presumably via cygserver). Services are run by 'cygrunsrv', not 'cygserver'. 'cygserver' provides Unix shared memory and IPC services for Cygwin. The upside is that it would probably make more sense to those coming to X from a Windows background. The downside is that there are so many different ways to start X (i.e. local/remote, multiwindow/external WM etc.) that you'd still need to support the traditional startup methods. Well, I don't recall if XWin has a way of selecting the next available display (I do know it's not on by default, even if it exists), but that would be pretty much a must in coping with an X service when one needs to also start an XDMCP query, for example. I know zip about the issues involved in running as a Windows service, but if it's simple, it may be something to consider, perhaps as a default installation. It's pretty simple to start a program as a service. One wouldn't want to have it as a default option, certainly, but a config script akin to that of other service packages (e.g., cron, openssh, cygserver, etc) that *installs* such a service for the user to start would be very useful. As a sidenote, historically (IMHO), X startup has been a bit of a mess. A lot of old X servers were started by running X and a WM in the background, then running xterm as a foreground task, just to enable switching (or more likely restarting) window managers. If they inadvertently closed the initial xterm, the poor user was stuffed! I know - I was that user! It would be trivial to write a keepX program that connects to the server and does nothing (but is a client, so X stays around even if no other clients are present). If such a program were contributed to the xorg packages (or, better yet, the upstream X distribution), the default xinitrc could invoke it in the background before the xterm. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
RE: Multiple XWin.exe programs loading and no xterm
On Thursday, March 31, 2005 7:10 PM, Alexander Gottwald wrote: On Thu, 31 Mar 2005, Armbrust, Daniel C. wrote: Because I execute the entire script twice, since the first execution doesn't bring up any xterms. Still not sure what is causing it to take so long to launch the xwin.exe. Can I set the timeout values on the xterm's with a flag? no. Use sleep to delay starting the xterms When I first started using Cygwin/X, I found that XWin.exe returns before it is really ready for business. This means that commands in startxwin.bat/whatever, such as xhost or xmodmap, try to communicate with the server while it is still initialising. To get around this, I added the following kludge to my startxwin.bat. It is essentially the same as the sleep solution, except that it only sleeps for as long as is necessary. If X is started by Windows startup, all manner of delays may mean that the sleep time that works 90% of the time will be too short 10% of the time. It works by waiting for the line to appear in the log file that announces its success. This hack has to go *immediately* after XWin.exe is started. You'll probably find that the line to set LASTLINE has become wrapped. Everything from SET to the second is a single line. People using startx will need a similar solution, but will be able to use more elegant code instead of the unholy mess that CMD.EXE forced me to write! ---8 set XWIN_LOG=%CYGWIN_TMP%\XWin.log set LASTLINE=XOpenDisplay () returned and successfully opened the display. set /a COUNT=0 :WAITFORLOG echo ...Waiting for X log file... sleep 1 set /a COUNT+=1 if not exist %XWIN_LOG% goto WAITFORLOG if %COUNT% GEQ 10 goto WARNFINISHOFF set /a COUNT=0 :WAITFORIT echo ...Waiting for X to complete initialisation... sleep 1 set /a COUNT+=1 if %COUNT% GEQ 30 goto WARNFINISHOFF %SYSTEMROOT%\system32\find.exe %LASTLINE% %XWIN_LOG% nul if errorlevel 1 goto WAITFORIT echo X started OK goto FINISHOFF :WARNFINISHOFF echo WARNING: X doesn't appear to have started cleanly sleep 5 :FINISHOFF --8--- Not pretty, but it WFM. Note1: %CYGWIN_TMP% is the location of cygwin's /tmp as returned by the command cygpath -d /tmp. Note2: The actual value used for LASTLINE should be taken from your own XWin.log following a successful start. As its name suggests, it's the last line from the file. (I.e. AFTER XWin.exe has really finished, but BEFORE any clients have been started) Note3: it uses windows' find.exe rather than cygwin's grep, because grep isn't (or wasn't) part of a minimal installation. Note4: if you hack startxwin.bat, save it under a different name e.g. mystartx.bat otherwise, the next time you update X, you'll lose your changes (you may detect the voice of bitter experience here ;-) Note5: There are too many notes for such a short bit of code! Of course, the *real* solution is for XWin to return only when it has completed ALL of its initialisation. My home PCs are now certified 100% Microsoft free :-), and there is no chance of me getting time to look at this at work, so unless someone else is prepared to do it, the above will have to suffice. Anyway, the above WFM, it may help solve some of the other problems people have been having with start-up. HTH, Phil -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
RE: Multiple XWin.exe programs loading and no xterm
On Thu, 7 Apr 2005, Phil Betts wrote: People using startx will need a similar solution, but will be able to use more elegant code instead of the unholy mess that CMD.EXE forced me to write! No. Startx uses xinit and xinit tries to connect to the xserver in the way a client would do and repeats it until the server is ready. Of course, the *real* solution is for XWin to return only when it has completed ALL of its initialisation. XWin does not return or anything like that. It's the way the process start works. You can either start a program and wait until it finished or continue right after the program started running. There are no simple mechanisms to send notice about finished startup. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Multiple XWin.exe programs loading and no xterm
--On 07 April 2005 14:21 +0200 Alexander Gottwald wrote: No. Startx uses xinit and xinit tries to connect to the xserver in the way a client would do and repeats it until the server is ready. That suggests another way to wait for the server. Run some suitably harmless (side-effect free) client in a loop until it succeeds before launching the xterm. xrdb -query seems a reasonable candidate. -- Owen Rees Hewlett Packard Laboratories, Bristol, UK
RE: Multiple XWin.exe programs loading and no xterm
On Thursday, April 07, 2005 1:21 PM, Alexander Gottwald wrote: On Thu, 7 Apr 2005, Phil Betts wrote: People using startx will need a similar solution, but will be able to use more elegant code instead of the unholy mess that CMD.EXE forced me to write! No. Startx uses xinit and xinit tries to connect to the xserver in the way a client would do and repeats it until the server is ready. I'll bow to your superior knowledge, it's about 10 years since I last used startx in anger, and that was on Linux, where the X servers only exit on closedown. However (I'm just speculating here) the problems I was having with xhost/xmodmap were partly that the client programs thought they had executed correctly (i.e. no errors were raised and the return code was zero). Is it possible that xinit similarly thinks all is well? Of course, the *real* solution is for XWin to return only when it has completed ALL of its initialisation. XWin does not return or anything like that. It's the way the process start works. You can either start a program and wait until it finished or continue right after the program started running. There are no simple mechanisms to send notice about finished startup. Reading between your lines, I assume you're saying that XWin is a regular Windows program, and it's all down to the way that WinMain is called. On Unixen, one would initialise first and then fork, to detach the server (or, more likely, leave it to the shell to place the server in the background), but I guess this is not practicable in a Windows environment. I'm happy with my hack for now, so I'm certainly not pushing for a change. Feel free to incorporate it into the distributed startxwin.bat if you want, although if you do, you may need to change the server to output a key phrase (e.g. XWin Initialisation Complete) that is always output regardless of how it was started, instead of my more ad-hoc approach. Cheers, Phil ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
RE: Multiple XWin.exe programs loading and no xterm
On Thu, 7 Apr 2005, Phil Betts wrote: I'll bow to your superior knowledge, it's about 10 years since I last used startx in anger, and that was on Linux, where the X servers only exit on closedown. However (I'm just speculating here) the problems I was having with xhost/xmodmap were partly that the client programs thought they had executed correctly (i.e. no errors were raised and the return code was zero). Is it possible that xinit similarly thinks all is well? I don't think so. Reading between your lines, I assume you're saying that XWin is a regular Windows program, and it's all down to the way that WinMain is called. On Unixen, one would initialise first and then fork, to detach the server (or, more likely, leave it to the shell to place the server in the background), but I guess this is not practicable in a Windows environment. Nothing forks except bash (or cmd or whatever) The xserver on unix does not put itself to background. It starts, accepts connections and exits sometime. Putting it in the background is exactly done by bash on Xorg or by cmd.exe on start XWin. I start XWin with a single shortcut. And clients later as I need them. Putting the xterm in the startup script is just for convenience and for preventing silly postings I started startxwin.bat and there is nothing happening. Now people at least see a window. But then they complained Calling startxwin.bat twice pops up an error message stating I started the xserver twice. This is just the third problem with a feature I consider completly useless. Maybe I should remove it and point the poeple to the users guide instead. I'm happy with my hack for now, so I'm certainly not pushing for a change. Feel free to incorporate it into the distributed startxwin.bat if you want, although if you do, you may need to change the server to output a key phrase (e.g. XWin Initialisation Complete) that is always output regardless of how it was started, instead of my more ad-hoc approach. Sorry. I won't make any move towards adding a hack into the startup scripts. First thing people should do is fix their systems and remove the crappy zone alarm and symantec antivirus programs. They cause the problems (at least they did in all other cases which were reported over the last months). If someone does not want to remove them, they should start debugging cygwin.dll and find a solution to let the process startup work properly even with zone alarm in place. Something I don't have time for. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Multiple XWin.exe programs loading and no xterm
On Wed, 30 Mar 2005, Armbrust, Daniel C. wrote: The -kb command helped with one of my machines that was having intermittent difficulties in launching. On another machine, however, I always have to execute the following script twice before I get any Xwin windows: run XWin -multiwindow -clipboard -silent-dup-error -kb run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash -l run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y [EMAIL PROTECTED] The first time that I run it - Xwin.exe and two xterm.exe's appear in the process manager - then both xterm's disappear. Eventually the X finally appears in the lower right corner. This means XWin is taking very long to startup. Maybe because of a virus scanner? The xterms will timeout after no connection to the xserver could be established. The second xserver will notice the first one and will silently exit but now the xterms can connect to the first xserver. Adding a sleep after run XWin might help by postponing the xterm startup. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Multiple XWin.exe programs loading and no xterm
I'm just trying to understand this even though it works for me now. Why are two X servers launching in the first place? --- Alexander Gottwald [EMAIL PROTECTED] wrote: On Wed, 30 Mar 2005, Armbrust, Daniel C. wrote: The -kb command helped with one of my machines that was having intermittent difficulties in launching. On another machine, however, I always have to execute the following script twice before I get any Xwin windows: run XWin -multiwindow -clipboard -silent-dup-error -kb run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash -l run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y [EMAIL PROTECTED] The first time that I run it - Xwin.exe and two xterm.exe's appear in the process manager - then both xterm's disappear. Eventually the X finally appears in the lower right corner. This means XWin is taking very long to startup. Maybe because of a virus scanner? The xterms will timeout after no connection to the xserver could be established. The second xserver will notice the first one and will silently exit but now the xterms can connect to the first xserver. Adding a sleep after run XWin might help by postponing the xterm startup. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723 Scott Cegielski [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
RE: Multiple XWin.exe programs loading and no xterm
Because I execute the entire script twice, since the first execution doesn't bring up any xterms. Still not sure what is causing it to take so long to launch the xwin.exe. Can I set the timeout values on the xterm's with a flag? Dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Cegielski Sent: Thursday, March 31, 2005 10:38 AM To: cygwin-xfree@cygwin.com Subject: RE: Multiple XWin.exe programs loading and no xterm I'm just trying to understand this even though it works for me now. Why are two X servers launching in the first place? --- Alexander Gottwald [EMAIL PROTECTED] wrote: On Wed, 30 Mar 2005, Armbrust, Daniel C. wrote: The -kb command helped with one of my machines that was having intermittent difficulties in launching. On another machine, however, I always have to execute the following script twice before I get any Xwin windows: run XWin -multiwindow -clipboard -silent-dup-error -kb run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash -l run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y [EMAIL PROTECTED] The first time that I run it - Xwin.exe and two xterm.exe's appear in the process manager - then both xterm's disappear. Eventually the X finally appears in the lower right corner. This means XWin is taking very long to startup. Maybe because of a virus scanner? The xterms will timeout after no connection to the xserver could be established. The second xserver will notice the first one and will silently exit but now the xterms can connect to the first xserver. Adding a sleep after run XWin might help by postponing the xterm startup. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723 Scott Cegielski [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
RE: Multiple XWin.exe programs loading and no xterm
I wasn'y reffering to your situation specifically. Even when the script is not executed twice, two Xwin.exe processes launch. That is what I described in the first post of this thread. As I learned, adding the -kb flag makes the second Xwin.exe die shortly after the initial launch, but my question is why two are loading in the first place. --- Armbrust, Daniel C. [EMAIL PROTECTED] wrote: Because I execute the entire script twice, since the first execution doesn't bring up any xterms. Still not sure what is causing it to take so long to launch the xwin.exe. Can I set the timeout values on the xterm's with a flag? Dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Cegielski Sent: Thursday, March 31, 2005 10:38 AM To: cygwin-xfree@cygwin.com Subject: RE: Multiple XWin.exe programs loading and no xterm I'm just trying to understand this even though it works for me now. Why are two X servers launching in the first place? --- Alexander Gottwald [EMAIL PROTECTED] wrote: On Wed, 30 Mar 2005, Armbrust, Daniel C. wrote: The -kb command helped with one of my machines that was having intermittent difficulties in launching. On another machine, however, I always have to execute the following script twice before I get any Xwin windows: run XWin -multiwindow -clipboard -silent-dup-error -kb run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash -l run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y [EMAIL PROTECTED] The first time that I run it - Xwin.exe and two xterm.exe's appear in the process manager - then both xterm's disappear. Eventually the X finally appears in the lower right corner. This means XWin is taking very long to startup. Maybe because of a virus scanner? The xterms will timeout after no connection to the xserver could be established. The second xserver will notice the first one and will silently exit but now the xterms can connect to the first xserver. Adding a sleep after run XWin might help by postponing the xterm startup. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723 Scott Cegielski [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ Scott Cegielski [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
RE: Multiple XWin.exe programs loading and no xterm
On Thu, 31 Mar 2005, Scott Cegielski wrote: I wasn'y reffering to your situation specifically. Even when the script is not executed twice, two Xwin.exe processes launch. That is what I described in the first post of this thread. As I learned, adding the -kb flag makes the second Xwin.exe die shortly after the initial launch, but my question is why two are loading in the first place. The XKB extension calls xkbcomp (an external program). This is done via fork. This means for a short time there are two XWin processes but one of them is transformed into an xkbcomp process later (check unix semantics for fork and exec for details). In some cases (textmode mounted /tmp, Personal firewalls and virus scanners) break the fork/exec calls. BTW: I've not heard any definitive answer if you have any of the above mentiond programs running. Disabling the XKB extension will result in not calling xkbcomp, so the lock disappears. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Multiple XWin.exe programs loading and no xterm
On Thu, 31 Mar 2005, Armbrust, Daniel C. wrote: Because I execute the entire script twice, since the first execution doesn't bring up any xterms. Still not sure what is causing it to take so long to launch the xwin.exe. Can I set the timeout values on the xterm's with a flag? no. Use sleep to delay starting the xterms bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Multiple XWin.exe programs loading and no xterm
On Tue, 29 Mar 2005, Scott Cegielski wrote: For me, putting a pause at the end of startxwin.bat does not make it work. However, I have found something that does seem to work for me. When I launch statxwin.bat, in addition to the 2 XWin.exe processes, there is also a sh.exe process that starts which I assume is from the MS-DOS shell that the .bat is run from. Even though the shell window closes after the script finishes, the sh.exe process is still running. If I open the task manger and end the sh.exe process, the xterm pops open and the extra XWin.exe goes away. Does anyone know why this sh.exe process whould linger around or how to kill it without having to open the task manager and mouse to it every time? This is from the xkbcomp call. Add -kb to the xwin commandline and it will not be started but the keyboard layout will be us only. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Multiple XWin.exe programs loading and no xterm
The -kb command helped with one of my machines that was having intermittent difficulties in launching. On another machine, however, I always have to execute the following script twice before I get any Xwin windows: --CUT-- All of the standard startXWin.bat environment setup stuff... --CUT-- run XWin -multiwindow -clipboard -silent-dup-error -kb run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash -l run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y [EMAIL PROTECTED] The first time that I run it - Xwin.exe and two xterm.exe's appear in the process manager - then both xterm's disappear. Eventually the X finally appears in the lower right corner. Then I run the script again, and this time the xterms actually launch. Here is the log file from the first launch: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-1 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error -kb ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (==) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () winInitMultiWindowWM - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (++) XkbExtension disabled (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. Does this shed any light on things? Thanks, Dan
RE: Multiple XWin.exe programs loading and no xterm
For me, adding -kb to the xwin command did work. Thanks much for the help. --- Armbrust, Daniel C. [EMAIL PROTECTED] wrote: The -kb command helped with one of my machines that was having intermittent difficulties in launching. On another machine, however, I always have to execute the following script twice before I get any Xwin windows: --CUT-- All of the standard startXWin.bat environment setup stuff... --CUT-- run XWin -multiwindow -clipboard -silent-dup-error -kb run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash -l run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y [EMAIL PROTECTED] The first time that I run it - Xwin.exe and two xterm.exe's appear in the process manager - then both xterm's disappear. Eventually the X finally appears in the lower right corner. Then I run the script again, and this time the xterms actually launch. Here is the log file from the first launch: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-1 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error -kb ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (==) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () winInitMultiWindowWM - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (++) XkbExtension disabled (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. Does this shed any light on things? Thanks, Dan Scott Cegielski [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Multiple XWin.exe programs loading and no xterm
On Mon, 28 Mar 2005, Scott Cegielski wrote: Hello, Please help. This is my first time trying to start X windows using cygwin although I have been using cygwin for a while now. I am running it like this: 1. Open cygwin bash shell 2. Type startxwin.bat The problem is that not much happens after that except that an X icon shows up in the windows task bar. If I open the windows Task Manager, I can see that there are two XWin.exe programs running. There is also an xterm.exe running, although I cannot see it on my screen. I have tried killing one of the XWin.exe processes, but the xterm never opens. Do you have ZoneAlarm or other Personal Firewalls or Live Virusscanners installed? The interfere with the cygwin network handling and will break Cygwin/X. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Multiple XWin.exe programs loading and no xterm
I did also try startx. Please see my original email for the output of startx. thanks --- Steven Boothe [EMAIL PROTECTED] wrote: Scott Cegielski wrote: Hello, Please help. This is my first time trying to start X windows using cygwin although I have been using cygwin for a while now. I am running it like this: 1. Open cygwin bash shell 2. Type startxwin.bat Try typing startx at the command line. What happens then? Scott Cegielski [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
RE: Multiple XWin.exe programs loading and no xterm
This happens to me all the time - I usually have to launch the X stuff 2 or 3 times before it actually works. I have to manually kill off all xterm.exe, bash.exe, and other cygwin programs in between the launches. I keep meaning to look into it more, but since I start it less than once a week, I haven't had enough incentive to dig deeper yet. I just set up cygwin on another machine this week, and it suffers the same problem. Dan
Re: Multiple XWin.exe programs loading and no xterm
Armbrust, Daniel C. wrote: This happens to me all the time - I usually have to launch the X stuff 2 or 3 times before it actually works. I have to manually kill off all xterm.exe, bash.exe, and other cygwin programs in between the launches. I keep meaning to look into it more, but since I start it less than once a week, I haven't had enough incentive to dig deeper yet. I guess I'm not alone. I've managed to solve this problem with the following hack: I add a pause command to the end of startxwin.bat. I forget why I tried this, but it works.
Re: Multiple XWin.exe programs loading and no xterm
For me, putting a pause at the end of startxwin.bat does not make it work. However, I have found something that does seem to work for me. When I launch statxwin.bat, in addition to the 2 XWin.exe processes, there is also a sh.exe process that starts which I assume is from the MS-DOS shell that the .bat is run from. Even though the shell window closes after the script finishes, the sh.exe process is still running. If I open the task manger and end the sh.exe process, the xterm pops open and the extra XWin.exe goes away. Does anyone know why this sh.exe process whould linger around or how to kill it without having to open the task manager and mouse to it every time? --- Jack Tanner [EMAIL PROTECTED] wrote: Armbrust, Daniel C. wrote: This happens to me all the time - I usually have to launch the X stuff 2 or 3 times before it actually works. I have to manually kill off all xterm.exe, bash.exe, and other cygwin programs in between the launches. I keep meaning to look into it more, but since I start it less than once a week, I haven't had enough incentive to dig deeper yet. I guess I'm not alone. I've managed to solve this problem with the following hack: I add a pause command to the end of startxwin.bat. I forget why I tried this, but it works. Scott Cegielski [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Multiple XWin.exe programs loading and no xterm
Scott Cegielski wrote: Hello, Please help. This is my first time trying to start X windows using cygwin although I have been using cygwin for a while now. I am running it like this: 1. Open cygwin bash shell 2. Type startxwin.bat Try typing startx at the command line. What happens then?
