This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
sh.exe hangs, but I can kind of get things working if I don't disable McAffee
- From: "Linda Yee" <dizzy_bird_ at hotmail dot com>
- To: cygwin-xfree at cygwin dot com
- Date: Wed, 19 Jan 2005 23:03:10 -0700
- Subject: sh.exe hangs, but I can kind of get things working if I don't disable McAffee
- Bcc:
- Reply-to: cygwin-xfree at cygwin dot com
If I don't disable Privacy Service:
If I run /usr/X11R6/bin/startxwin.sh (from bash without calling sh), the
script gets to
===============================================================
...
XFree86-Bigfont extension local-client optimization disabled due to lack of
shar
ed memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409)
(--) Using preset keyboard for "English (USA)" (409), type "4"
Rules = "xorg" Model = "pc105" Layout = "us" Variant = "(null)" Options =
"(null
)"
===============================================================
If I press Enter at this point, I get a command prompt.
ps indicates that I have bash, xterm, XWin, and sh (child of XWin) running.
I don't see an xterm.
I try to run xdvi. It shows up in the process list, but I don't see an
xdvi window.
In order to get xdvi running, I first have to type in
export DISPLAY=127.0.0.1:0.0
If I open another cygwin prompt and kill -9 /usr/bin/sh from it, XWin spits
out:
===============================================================
$ (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing
from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing
from
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing
from
list!
winPointerWarpCursor - Discarding first warp: 700 525
winInitMultiWindowWM - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - 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
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the
disp
lay.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened
the di
splay.
winClipboardProc - XOpenDisplay () returned and successfully opened the
display.
Xlib: sequence lost (0x13501 > 0x188) in reply type 0x82!
Xlib: unexpected async reply (sequence 0x3501)!
X connection to 127.0.0.1:0.0 broken (explicit kill or server shutdown).
===============================================================
At this point, xdvi pops up (but is non-functional). A completely
functional
xterm pops up. If I set the DISPLAY properly on both cygwin windows, I can
call
gv, xfig, xeyes, xpdf, xterm, xemacs, etc--they all work, although xdvi is
still
unhappy and vanishes the moment the cursor is over it.
Etc, etc. So, everything that I've tried except xdvi is fine, except when I
try
to exit from cygwin. I have to kill -9 XWin.
===============================================================
On the other hand, if I disable McAffee Privacy Service before starting
cygwin, on calling starwin.sh, I get
===============================================================
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409)
(--) Using preset keyboard for "English (USA)" (409), type "4"
winMultiWindowXMsgProc - Hello
ayout = "us" Variant = "(null)" Options = "(null)"
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
===============================================================
killing /usr/bin/sh leads to
===============================================================
$ (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing
from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing
from
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing
from
list!
winPointerWarpCursor - Discarding first warp: 700 525
winInitMultiWindowWM - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - 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
XIO: fatal IO error 22 (Invalid argument) on X server "127.0.0.1:0.0"
after 5 requests (4 known processed) with 0 events remaining.
XIO: fatal IO error 22 (Invalid argument) on X server "127.0.0.1:0.0"
after 5 requests (4 known processed) with 0 events remaining.
winClipboardIOErrorHandler!
===============================================================
This time, though, killing sh kills its parent XWin. Exiting from cygwin
is
not a problem.
Why does XWin.exe spawn sh.exe? What is it doing? How is it interacting
with
the firewall?
Well, I guess I'm hoping mostly that someone can fix things.
_________________________________________________________________
Take advantage of powerful junk e-mail filters built on patented Microsoft®
SmartScreen Technology.
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
Start enjoying all the benefits of MSN® Premium right now and get the
first two months FREE*.