Weird Xwindows situations...
I've got an xwindows application that I'm running on a PC through CygwinX. What's going on is it's acting as if it's sending a mouse click when it's just being moved. And it seems to be acting as if it's click at the same location each time. (ie it's activating one of my buttons without actually clicking the button.) Is there anyway to get a debug log of mouse clicks and movement? Or does anyone have any suggestions? If you start typing in the window and then go to move the mouse anywhere on the screen it will act as if the cancel button has been clicked. Thoughts? -- 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/
Windowmaker not open bash properly
I had Cygwin with Windowmaker running just beautifully, then another application came in and installed another xserver (which I've since disabled) but now inside windowmaker, whenever I try to open up an Xterm window the window opens but I get no bash prompt. I can type an ls and get a file listing, and a ps gives me processes. However whenever I try to ssh -Y to another machine, it tells me Pseudo-terminal will not be allocated because stdin is not a terminal. Anyone ever seen this before, and a solution? Scott Mohnkern -- 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: Windowmaker not open bash properly
Scott Mohnkern wrote: I had Cygwin with Windowmaker running just beautifully, then another application came in and installed another xserver (which I've since disabled) but now inside windowmaker, whenever I try to open up an Xterm window the window opens but I get no bash prompt. I can type an ls and get a file listing, and a ps gives me processes. However whenever I try to ssh -Y to another machine, it tells me Pseudo-terminal will not be allocated because stdin is not a terminal. Anyone ever seen this before, and a solution? I'd suggest reading the problem reporting guidelines outlined at the link below: Problem reports: http://cygwin.com/problems.html You've given us some information about how the problem manifests itself but it would be helpful to know what other Xserver you installed as well as basic boot-strap information (i.e. cygcheck output - *attached* not included/inlined). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - 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: Windowmaker not open bash properly
Scott Mohnkern wrote: Apologies, I was following the format of other questions I'd seen here. Attached is cygcheck.out The other server was Xvision, which was part of an automatic install of Cradle 5.5.x You (no longer?) have Cygwin in your path. You're picking up the Nutcracker/MKS tools now. Fix your path and give a quick run through of the rest of your environment to clean up any issues. Two that caught my eye are $HOME and $TERM are now incorrectly set. If you can find where Nutcracker/MKS sets these and remove/avoid them, you'll have better luck working with Cygwin. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - 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: Windowmaker not open bash properly
Scott Mohnkern wrote: Larry Hall (Cygwin X) wrote: Scott Mohnkern wrote: Apologies, I was following the format of other questions I'd seen here. Attached is cygcheck.out The other server was Xvision, which was part of an automatic install of Cradle 5.5.x You (no longer?) have Cygwin in your path. You're picking up the Nutcracker/MKS tools now. Fix your path and give a quick run through of the rest of your environment to clean up any issues. Two that caught my eye are $HOME and $TERM are now incorrectly set. If you can find where Nutcracker/MKS sets these and remove/avoid them, you'll have better luck working with Cygwin. That appears to have solved most of it. Removing the nutcracker entries and putting cygwin and cygwin bin in the path got me up and running. It doesn't appear to be pulling my profile up correctly when I open up bash (It's defaulting to a different $HOME but I can probably figure out where that is set) It's probably in your system-level environment, which you can access from the Windows control panel System applet. Good luck. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - 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/
