Re: bug report/suggested temp. patch: handling bursts of sent keys
> Larry Hall wrote: > On 01/19/2010 01:17 PM, Mark Lillibridge wrote: > > > > Hi. > > > >I don't appear to have gotten any response to my message sent to > > this list January 12 (copied below). Do I have the right list? Am I > > supposed to use a different mechanism to report bugs with the Cygwin X > > server? Please help. > > Thanks for the information you've provided. This is the correct list for > Cygwin X issues. I can't engage you on this topic because I'm not > knowledgeable about the area you investigated. However, a couple of > questions come to my mind about what you've found: > > 1. Is this Cygwin-specific? The Xming server, which I understand shares source code, also has this bug. The commercial X server, Reflection, does not have this bug. This bug is specific to Windows implementations so I presume it does not belong in the generic Xorg source. > 2. If not, what's the upstream solution? > > > This information might help you decide if your issue is better reported > upstream. It may also help developers here decide how to solve the > 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/
Mouse right-click doesn't work when working with exported windows
Hello all, I'm facing a strange problem here, hope that someone could help. When I start Cygwin/X and open a graphical application such as "nedit", I can right-click and get the proper context menus, regardless of the Num-lock state. But when I log on to any of our servers via "ssh -X" or rlogin from within xterm and I start any graphical app (exporting the window to my desktop), the behaviour is as follows: - With Num-lock on, right-clicking does nothing. No context menu appears; - With Num-lock off, the cursor flips (it points to the right instead of the left), and then both the mouse and the keyboard stops responding, even on xterm. I'm forced to shut down the Cygwin/X server. As I said, this error only occurs when working with exported windows of any application, regardless of the server (tried with both Red Hat EL5 and HP-UX 11.* ones). My desktop is Windows XP Pro SP3, and I'm using the latest version of Cygwin. Attached is the output of cygcheck and from the XWin log. I used the xev utility to check if there are differences on the output when clicking on a local window and a remote one: no difference perceived. Curiously, I can work properly when using Cygwin 1.5.x, as it's already installed on some machines, but I couldn't get it to work using the setup-legacy.exe. It installs but no command is recognized (maybe something related to path setting, but I'll research more and post on the proper list if necessary). Any clues on how to solve it? Regards, Daniel cygcheck.out Description: Binary data XWin.0.log Description: Binary data -- 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: 1.7.1: no xdmcp login prompt after upgrade
That is a good suggestion; I will try that this weekend. Should that prove to work, would that then suggest something in Cygwin/X's name resolution is broken? This worked "as-is" under 1.5.25; it is broken under 1.7.1 - what changed? Respectfully, D. Michael Paxton, Esq., MBA FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Holger Krull Sent: Friday, 22 January 2010 08:47 To: cygwin-xfree@cygwin.com Subject: Re: 1.7.1: no xdmcp login prompt after upgrade Am 15.01.2010 21:32, schrieb Paxton, Michael: > After upgrading to Cygwin/X 1.7.1, XDMCP query to any remote host no > longer produces a login prompt. All XDMCP connections functioned > correctly prior to upgrade. > > Examination of an iptrace report (ipreport10.out) on the remote host > shows that Cygwin/X is not continuing the connection sequence after the > remote host replies to the initial port 177 communication. Did you try to do use numeric ip addresses and the -from switch to see if it produces a different result? Like: XWin -query xdmcp.numeric.host.address -from your.own.numeric.address -- 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/ -- 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: 1.7.1: no xdmcp login prompt after upgrade
Am 15.01.2010 21:32, schrieb Paxton, Michael: After upgrading to Cygwin/X 1.7.1, XDMCP query to any remote host no longer produces a login prompt. All XDMCP connections functioned correctly prior to upgrade. Examination of an iptrace report (ipreport10.out) on the remote host shows that Cygwin/X is not continuing the connection sequence after the remote host replies to the initial port 177 communication. Did you try to do use numeric ip addresses and the -from switch to see if it produces a different result? Like: XWin -query xdmcp.numeric.host.address -from your.own.numeric.address -- 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 with startxwin.exe and a possible solution
--- Ven 22/1/10, Charles Wilson ha scritto: > Marco Atzeri wrote: > > Today I start some experiments and I have found that > > changing the menu target from > > > > C:\cygwin2\bin\run.exe /usr/bin/bash.exe -l -c > /usr/bin/startxwin.exe > > > > to > > > > C:\cygwin2\bin\run.exe -p /usr/bin > /usr/bin/startxwin.exe > > > > all the problems seem gone. > > The Xserver is stable and all the Xterms run > smoothly. > > > > I suppose that my login shell redefine some parameters > that > > startxwin.exe needs, while a much simpler > > "run.exe -p /usr/bin" is what is really needed. > > The real issue, I think, is that your mechanism doesn't > allow you to set > OTHER environment variables that might need to be defined > before > launching XWin, such as LC_ALL etc -- which would get set > by the > original formula, since 'bash -l' reads your startup files > like > ~/.bash_profile where they might get set. > As on my .bash_profile, I don't set LC_ALL and I just clean PATH and redirect TEMP and TMP, I have not such problem. However I just tested that C:\cygwin2\bin\run.exe -p /usr/bin /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe is also working as expected. Using such target I have 3 process: bash.exe startxwin.exe Xwin.exe I just checked with Process Explorer the enviroment and I find that, for both bash and startxwin.exe, PATH is not the one I have in .bash_profile.. For the bash process this does make sense, but startxwin.exe should have the PATH redefined. If I run from a bash-xterm login session another bash -l, Process Explorer reports the first with the windows PATH but the second with the redefined PATH as the first is a login shell and followed .bash_profile. It is like the "-c" option of bash is blocking the "-l" option. As my Windows PATH don't include the cygwin /usr/bin, without the "-p /usr/bin" bash is crippled and so also startxwin.exe.. > -- > Chuck Marco -- 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/
