Re: Problem Starting X-Windows -- Problem solved

[wonder <wonder_6908 at yahoo dot com>]

Renà Berber <r.berber <at> computer.org> writes:

> 
> wonder wrote:
> [snip]
> > I have a similar problem with startx or whichever way to start X. 
It was all 
> > ok before. The problem happened since yesterday. It probably has 
to do with 
> > the installation of the McAfee Privacy Service module. 
This module might have
> > changed some settings on my computer. The symptom is that 
you can launch X
> > applications, but nothing pops out. There are one or more 
instances of sh.exe
> > running with (nearly) 100% CPU usage. Once you kill all sh.exe 
processes, the
> > xterms will show up on your desktop. But anything that relies on 
sh.exe will 
> > not be able to run. For example, you can try SSH with 
X11 forwarding enabled. 
> > But it will invoke sh.exe and therefore won't get connected 
until you kill
the newly
> > invoked sh.exe. Unfortunately, the X11 tunnel will be broken 
after sh.exe is
killed.
> > 
> > I hope I have described clearly. Anybody has a solution?
> 
> No, it's not clear.
> 
> 1. Does XWin starts fine? (is your question really about a 
problem starting XWin?)
> 
> 2. How do you "launch" X applications? (there shouldn't be 
any sh.exe started if
> you run something else)
> 
> 3. Does disabling McAfee helps?
> 


Just read a little further on this issue. It turns out that SSH.EXE 
does call sh.exe or cmd.exe in order to pass certain parameters. 
But I don't know in which case ssh.exe does which. Somewhere 
I remember it says when sh.exe is available,
ssh.exe will launch it. So my simple solution is just to rename 
sh.exe to something else. Then everything goes back to normal, 
and ssh.exe does not complain at all about missing sh.exe. 

PS. I cannot find a way to uninstall the McAfee Privacy Service 
component alone (once installed) without uninstalling the entire 
McAfee package. 

I did some tests before I found the above solution. It seems any 
other X applications (e.g., xterm) launches fine once XWin is up 
and running (after one
kills sh.exe), as long as this application does not call sh.exe. 
One thing I didn't describe accurately in my last post was that 
the X tunneling was actually NOT broken after sh.exe was killed.

I hope this info is useful to other people who suffer from 
the same sh.exe problem. 


--
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/