Re: Problem Starting X-Windows -- Problem solved
wonder, Your solution didn't cut it for me. I have McAfee as well so I thought we may have the same problem. However, after I renamed 'sh.exe', I've noticed the same problem persist. It turns out whenever I initiate the Cygwin Bashshell, a new sh.exe is generated in the /bin folder :( Could more ideas? Thanks for sharing your experiences, I am sure you have pull many hairs like myself. -Dean -- 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 Starting X-Windows -- Problem solved?
I have also seen the same Cygwin/startx problem that Dean C. Tsai reported on 15 Feb 2006, and I have found the same workaround, killing the sh.exe process that's hogging the CPU. I don't know what's causing it, either. I tried the latest suggestion, renaming sh.exe before running startx, but I got an immediate error message bad interpreter: No such file or directory and the $ prompt, with no X window and no Winit or x* processes running. I, like wonder_6908, have McAfee Privacy Service running -- but when I disabled it, the problem remained. I also disabled the rest of the McAfee Security Center -- VirusScan, Personal Firewall Plus, and SpamKiller. The problem remained. Unlike Dean, I have a Gateway NX500X, not a Dell. I've had this problem since the computer was brand-new (the first of the year), and I have not modified the keyboard configuration. I'll keep watching for resolution. (I tried posting a similar message last week, following up on a more general posting I'd sent a month earlier, prior to this stream. I don't see either message in the archive, so I'm trying again.) Bill Page -- 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 Starting X-Windows -- Problem solved?
On 03/06/2006, Bill Page wrote: I have also seen the same Cygwin/startx problem that Dean C. Tsai reported on 15 Feb 2006, and I have found the same workaround, killing the sh.exe process that's hogging the CPU. I don't know what's causing it, either. I tried the latest suggestion, renaming sh.exe before running startx, but I got an immediate error message bad interpreter: No such file or directory and the $ prompt, with no X window and no Winit or x* processes running. I, like wonder_6908, have McAfee Privacy Service running -- but when I disabled it, the problem remained. I also disabled the rest of the McAfee Security Center -- VirusScan, Personal Firewall Plus, and SpamKiller. The problem remained. Typically, when McAffee and Norton cause problems, it is not sufficient to just disable them. You have to uninstall them to make a real test. So McAfee still may be getting in your way and the root cause of this problem for you. If you have the option, you may want to consider uninstalling it it and repeating the test. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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 Starting X-Windows -- Problem solved
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/
Re: Problem Starting X-Windows
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? -- René Berber -- 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 Starting X-Windows
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: (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 then in your second message the error appears: (EE) Couldn't open compiled keymap file /tmp/server-0.xkm (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap so it looks like you changed something or what you mean is that startx hung just after the keyboard messages and when you killed it the (EE) messages appear? I think this is more of a Xfree86 problem but I don't know how to get more information out of the startup. One thing that may be usefull is to see what process is really hung. It has to be a child of the shell (startx) and it may be xkbcomp or something else. -- René Berber -- 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 Starting X-Windows
hey Rene, Thanks so much for your assistance... However it still didn't solve the problem :( I tried to spawn an instance of xterm via Programs Cygwin-X Xterm... didnt work. I edited my own .xinitrc in the home directory... didn't work. I reinstall X-startup-scripts-1.0.11-1 and Xterm... didn't work either. The good news is, I have ways around the problem now. I noticed that when my Win32 prompt stop scrolling a sh.exe process is taking 99% of my CPU processing. If I go ahead and kill that process... I got this display from the screen followed by an xterm window!! I did find something on Cygwin faq http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xkb-not-working I will investigate into this a little more when I go home today. Hopefully this will solve my problem... Do you think it will? Thanks a bunch! -Dean ... (EE) Couldn't open compiled keymap file /tmp/server-0.xkm (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/CID/, removing from List! winInitMultiWindowWM - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winInitClipboard () winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winProcEstablishConnection - winInitClipboard returned. 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. winClipboardProc - Call to select () failed: -1. Bailing. winClipboardProc - XDestroyWindow succeeded. winClipboardIOErrorHandler! -- 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 Starting X-Windows
Dean Tsai wrote: Thanks so much for your assistance... However it still didn't solve the problem :( I tried to spawn an instance of xterm via Programs Cygwin-X Xterm... didnt work. I edited my own .xinitrc in the home directory... didn't work. I reinstall X-startup-scripts-1.0.11-1 and Xterm... didn't work either. The good news is, I have ways around the problem now. I noticed that when my Win32 prompt stop scrolling a sh.exe process is taking 99% of my CPU processing. If I go ahead and kill that process... I got this display from the screen followed by an xterm window!! I did find something on Cygwin faq http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xkb-not-working I will investigate into this a little more when I go home today. Hopefully this will solve my problem... Do you think it will? I don't know. The problem is then somewhere in the startup and is caused by an unknown keyboard layout? ... (EE) Couldn't open compiled keymap file /tmp/server-0.xkm (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap (--) 3 mouse buttons found Or is just a permission error? Try testing if you can create files in /tmp, something like touch /tmp/my-test and see if the (empty) file was created. -- René Berber -- 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/
