This is the mail archive of the cygwin-xfree mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem Starting X-Windows


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

> 
> Dean C. Tsai wrote:
> 
> > - NO, the Cygwin/X faq on keymap didnt solve my problem.
> > 
> > - I have a Dell Laptop w/ XP running. I am guessing the keyboard map is 
not 
> > the problem.
> > 
> > Permission error or not, I am not sure. However, I have created my-test in 
> > /tmp w/o problem...
> 
> OK, so you eliminated permissions and keyboard map as the cause.
> 
> > Do you have some idea about why and where "sh.exe" is called? I look 
through 
> > Cygwin/X's faq, it says very little about startup configuration. And I am 
> > embarrassed to admit that I don't know how to set option via command 
line?! 
> > .... I simple type 'startx' at the prompt. Do you know any good reference 
> > for X startup configuration?
> 
> The sh you killed is the one running startx, which is a shell script.

> 
> The error message "Couldn't open compiled keymap file" comes from 
xkbcomp.exe,

> but I'm confused here, in your first message the keyboard was recognized 
fine:



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?

Thanks,

wonder



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]